# Snowplow Signals > Signals tells you what your customer is doing right now so your product can respond while they are still on the page. Real-time customer context, by Snowplow. ## Pages - [Home](https://signals.snowplow.io/): Signals tells you what your customer is doing right now so your product can respond while they are still on the page. Real-time customer context, by Snowplow. - [Products](https://signals.snowplow.io/products): Event collection, real-time attributes, real-time triggers and agentic context. - [Solutions](https://signals.snowplow.io/solutions): Use cases and industries: personalization, ML features, customer-aware agents; media, retail, travel. - [Evaluate](https://signals.snowplow.io/evaluate): Signals compared to Tecton, Feast and Chalk, to feature stores and CDPs, and to building in-house. - [Pricing](https://signals.snowplow.io/pricing): Usage-based, metered on events and reads. A free tier, then a quote. - [Get started](https://signals.snowplow.io/start): Start on the free tier or book time with a solutions engineer. - [Architecture fit](https://signals.snowplow.io/architecture-fit): Describe your system and get the closest of the four Signals architectures. - [Blog](https://signals.snowplow.io/blog): How real-time customer context works, what we ship, and how teams use it. ## Products - [Event collection](https://signals.snowplow.io/products/event-collection): Event collection is built into Signals. Add the SDK and behavioral events from web, mobile and server flow in, schema-checked and ready for live attributes. - [Real-time attributes](https://signals.snowplow.io/products/real-time-attributes): Define what you want to know about a customer once. Signals computes it from live behavior, keeps it current and serves it in single-digit milliseconds. - [Real-time triggers](https://signals.snowplow.io/products/real-time-triggers): Real-time triggers evaluate conditions over live attributes and deliver the moment one is met, to your app or to Braze, Kafka, webhooks and Pub/Sub. - [Agentic context](https://signals.snowplow.io/products/agentic-context): Agentic context gives an agent a customer's recent activity as JSON or narrative, current as of now, so it can respond to what the customer is actually doing. ## Use cases - [In-session personalization](https://signals.snowplow.io/use-cases/in-session-personalisation): Change the page while the customer is still on it. Signals computes what this customer is doing on the event stream and hands it to whatever renders the page. - [Real-time features for ML](https://signals.snowplow.io/use-cases/model-features): Serve the features you trained on. One definition builds a point-in-time correct training set in your warehouse and serves the live value. - [Customer-aware AI agents](https://signals.snowplow.io/use-cases/customer-aware-agents): Give the agent the last five minutes. Signals hands it this customer's recent activity in a form a model can use, JSON or narrative, over an API or MCP. - [State for System One models](https://signals.snowplow.io/use-cases/system-one-models): System One models answer typed questions about the state you send. Signals hands them what the customer has been doing, as JSON or as a narrative. ## Industries - [Media & Publishing](https://signals.snowplow.io/solutions/media): Front pages, recommendations and paywalls decide the moment a reader arrives. Signals keeps the attributes they read current while the session is still running. - [Retail & E-commerce](https://signals.snowplow.io/solutions/retail): Baskets, listings, stores and sessions move faster than a nightly model. Signals keeps the attributes your storefront, search and service read current in-visit. - [Travel](https://signals.snowplow.io/solutions/travel): A traveler compares dates, swaps airports and abandons a fare in minutes. Signals keeps the attributes your search, booking and service surfaces read current. ## Comparisons - [Signals vs a feature store](https://signals.snowplow.io/evaluate/feature-stores): Where Signals overlaps with a feature store, where it does not, and when to run both. Written for architects who have already priced one. - [Build vs buy](https://signals.snowplow.io/evaluate/build-vs-buy): What an in-house real-time profile service costs after launch, row by row, and which parts are still worth building yourself. - [Signals vs a CDP](https://signals.snowplow.io/evaluate/cdps): A CDP unifies who someone is and pushes audiences to marketing tools. Signals computes what they are doing now and serves it in-request. Most teams keep both. - [Signals vs Tecton](https://signals.snowplow.io/evaluate/tecton): Where Signals and Tecton overlap on serving, where they differ on collection and warehouse neutrality, and when it makes sense to run both. - [Signals vs Feast](https://signals.snowplow.io/evaluate/feast): Feast is a framework you operate. Signals is a managed service that brings collection with it. Where the two overlap, and when to run both. - [Signals vs Chalk](https://signals.snowplow.io/evaluate/chalk): Chalk assumes your data sources exist. Signals collects the behavior first. Where the two overlap on serving, and when it makes sense to run both. ## Blog - [Decisions are a commodity now. Context is not.](https://signals.snowplow.io/blog/decisions-are-a-commodity-context-is-not): Four decision models shipped in two weeks and Databricks made one a SQL function. The model is cheap now. The state you hand it is not. - [Upgrading Signals to Valkey 9.1: 10% less memory, 28% less write time](https://signals.snowplow.io/blog/valkey-9): We replayed one Signals workload on Valkey 8.0 through 9.1. Memory per stored attribute fell 10% and server time per write fell 28%. ## Elsewhere - [Documentation](https://docs.snowplow.io/docs/signals/introduction/): Reference, guides, API and SDK documentation. - [Snowplow](https://snowplow.io): The platform Signals is part of. ## For agents - [API catalog](https://signals.snowplow.io/.well-known/api-catalog): The Signals API and the MCP server, as an RFC 9727 link set. - [MCP server card](https://signals.snowplow.io/.well-known/mcp/server-card.json): The MCP server at https://console.snowplowanalytics.com/api/agent/mcp, and how to authenticate with it. - [Agent skills](https://signals.snowplow.io/.well-known/agent-skills/index.json): A skill covering what Signals is for and how to start. - [Capability manifest](https://signals.snowplow.io/.well-known/ai-catalog.json): The same resources as an ARD catalog, for registries. - Any page on this site is served as markdown to a request that sends `Accept: text/markdown`.