An event is a data point generated by a website, app, server, or cloud application. For example, let’s say you’re browsing a website. When the page loads, that generates a page call that counts as 1 event.

Event limit overages are handled based on your plan.

• If you’re on the ​Free plan​, data processing will stop after your second consecutive overage. You can upgrade your plan at any time to ensure continuous data processing.
• If you’re on the ​Starter plan​, you’ll be charged overage fees once you exceed your plan’s event limit. The overage fee is calculated as the difference between the next tier’s pricing and your current plan’s pricing.

For more details, see our plan and billing management documentation.

Yes, we actively contribute to our self-hosted code as you can see on our GitHub page. The self-hosted project is released under Elastic 2.0. The core data processing layer is the same for both the Community and Enterprise edition. The Enterprise edition comes with some more advanced reporting & clustering features, but those are built on top of the data plane.

We don’t offer dedicated support, but we have a very active community on Slack where you can ask any questions. Join us here! If you’re on any of our paid plans, you'll have some level of support from our team. If you are on the Enterprise plan, you will have an account manager and a dedicated Slack channel.

RudderStack is warehouse-first and built for developers. Our goal is to help you build your customer data platform on top of your own data warehouse. We think your customer data should not live in a data silo where you need to run complex functions inside of a black box. For an in depth comparison, see our RudderStack vs Segment guide.

If you'd like a demo, you can fill out this form and we'll get back to you soon! You can also join our community of data professionals, or follow us on social media: Twitter or LinkedIn.

RudderStack Core is how data teams collect, govern, and unify customer data and stream it to every tool in real time. Lookout is how marketers analyze that data, build audiences, and activate them, just by asking. Core is priced on events. Lookout is priced on activated records.

No. Lookout runs on all of the data in your warehouse, from any source. If your team also runs RudderStack Core, Lookout builds on data that's already governed and unified.

Yes. You can get Core and Lookout on one contract. Talk to our team about pricing for both.

Reverse ETL is how your data team syncs the tables and models it builds to downstream tools, and each record it sends counts as an event on your Core plan. Lookout is how marketers find, build, and activate audiences themselves, without SQL or a ticket, and you pay once per person reached. You’re never double charged.

A person's first sync to a destination from an audience. Each person counts once per audience, per destination. One customer in two audiences, each synced to Meta and Braze, is four activated records.

Attribute updates, re-syncs at any frequency, removals, and conversations with Lookout. If someone leaves an audience and later rejoins it, that counts as a new activated record.

Additional records are billed at volume rates that get lower as you grow. You don't need to change plans.

You pay the plan price. It covers full access to Lookout and your included records.

Choose by volume, not company size. Growth costs less unless you activate a very high volume of records. Enterprise has a higher starting price and much lower rates at high volume, plus savings when you commit to an annual volume. Talk to our team and we'll help you estimate.

Yes. The Free plan includes 3 activations per year with up to 5,000 records per sync, so you can get your first audiences live before you buy.

See the full list in the Lookout docs.

RudderStack Core is how data teams collect, govern, and unify customer data and stream it to every tool in real time. Lookout is how marketers analyze that data, build audiences, and activate them, just by asking. Core is priced on events. Lookout is priced on activated records.

No. Lookout runs on all of the data in your warehouse, from any source. If your team also runs RudderStack Core, Lookout builds on data that's already governed and unified.

Yes. You can get Core and Lookout on one contract. Talk to our team about pricing for both.

Reverse ETL is how your data team syncs the tables and models it builds to downstream tools, and each record it sends counts as an event on your Core plan. Lookout is how marketers find, build, and activate audiences themselves, without SQL or a ticket, and you pay once per person reached. You’re never double charged.