Business Intelligence · head to head
Cabin vs Restate

Cabin
Business Intelligence
Cookieless web analytics that also reports the carbon footprint of your website
- From
- Free
- Free plan
- Yes

Restate
Developer Tools
Durable execution engine in Rust with a free tier and low-latency workflows
- From
- Free
- Free plan
- Yes
The short version
- Cabin is a privacy-first analytics tool.
- Free plans on both; paid from $14/mo and $300/mo.
- Only Cabin lists cookieless tracking; only Restate lists durable execution.
- Prices and features on this page were last checked on 31 August 2026.
Where they differ
Only the attributes on which Cabin and Restate actually diverge.
Identical on both: starting price (Free), free tier (Yes).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Cabin
- Cookieless tracking
- Carbon reporting
- 1.2kb script
- Custom events
- Ad-blocker bypass
- MCP access
- Branded dashboards
- EU data storage
Only in Restate
- Durable execution
- Virtual objects
- Single binary runtime
- Multi-language SDKs
- Workflows and sagas
- Restate Cloud
What people use each for
The jobs each tool is most often brought in to do.
Cabin
- Replacing Google Analytics on a site where a cookie consent banner is hurting conversion and you do not need behavioural advertising datanot Restate
- An organisation with a published sustainability commitment that needs a reportable figure for its website emissionsnot Restate
- An agency managing many client sites that wants unlimited domains and branded client dashboards for a flat $45 a monthnot Restate
- A developer who wants to query site analytics conversationally through an MCP-connected assistant rather than reading a dashboardnot Restate
Restate
- Payment or order flows where a crash between two external API calls must not double-charge or lose the ordernot Cabin
- AI agent loops that call tools over minutes or hours and must survive a deployment mid-runnot Cabin
- Replacing hand-rolled retry, idempotency key and outbox code across a set of microservicesnot Cabin
- A small team that wants durable workflows without operating a Temporal cluster and its databasenot Cabin
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cabin
- The analytics are deliberately shallow: no funnels, no cohort retention, no session replay and no user-level journeys, so anything beyond traffic and event counts requires a second tool
- Carbon figures are modelled from bytes transferred using CO2.js assumptions about grid intensity and device energy, not measured, so they are directionally useful and should never be presented as audited emissions data
- Cabin is a product of Normally, a design studio, rather than a company whose sole business is analytics, which puts a reasonable question mark over long-term roadmap investment and support depth
- The 30-day retention on the free tier and 12 months on Plus mean year-on-year comparison needs the $45 Scale plan, which is a large jump for a small site that only wanted longer history
- Because it does not use cookies or cross-site identifiers, returning-visitor and multi-session attribution are approximations, which matters if anyone in the business is trying to reconcile it with an ad platform's numbers
Restate
- The runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone
- Restate Cloud jumps from a free fifty thousand actions straight to 300 US dollars a month for twenty million, so a workload sitting at a few hundred thousand actions pays enterprise-shaped money for hobby-shaped volume
- It is a young project against Temporal’s established base, so hiring engineers who already know it is unrealistic and the answer to most questions is in the docs rather than on Stack Overflow
- The programming model requires structuring code around durable handlers and virtual objects, which is a genuine rewrite for existing services rather than a library you add
- The single-binary simplicity that makes small deployments cheap also means fewer operational knobs at very large scale than a system designed as separable components
Pricing, plan by plan
Cabin
Free- FreeFree
- 1 domain
- 10,000 pageviews per month
- 30-day data retention
- Plus$14/mo
- Up to 10 domains
- 100,000 pageviews per month
- 12-month retention
- Scale$45/mo
- Unlimited domains
- 5,000,000 pageviews per month
- Unlimited retention
Restate
Free- FreeFree
- Fifty thousand durable actions per month
- No credit card required
- Community support
- Starter$300/mo
- Twenty million actions per month
- Two hundred actions per second, bursting to one thousand
- Twenty GB storage
- Pro$1,000/mo
- Fifty million actions per month
- Five hundred actions per second, bursting to two thousand
- Fifty GB storage
- EnterpriseOn request
- Negotiated volume
- Twenty-four seven P0 support
- 99.99 per cent SLA
Which should you pick?
Choose Cabin if
- You need cookieless tracking.
- You want to start without paying.
- You also want carbon reporting.
Choose Restate if
- You need durable execution.
- You want to start without paying.
- You work on Linux, macOS, Web.
- You also want virtual objects.
Questions people ask
- Is Cabin or Restate better?
- Neither clearly leads. Cabin starts at Free and Restate at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cabin or Restate?
- Cabin starts at Free and Restate at Free.
- Does Cabin or Restate run on more platforms?
- Cabin runs on Web. Restate runs on Linux, macOS, Web.
- Can I use Cabin for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Cabin best used for?
- Cabin is most often used for replacing google analytics on a site where a cookie consent banner is hurting conversion and you do not need behavioural advertising data, an organisation with a published sustainability commitment that needs a reportable figure for its website emissions, an agency managing many client sites that wants unlimited domains and branded client dashboards for a flat $45 a month, a developer who wants to query site analytics conversationally through an mcp-connected assistant rather than reading a dashboard. Of those, replacing google analytics on a site where a cookie consent banner is hurting conversion and you do not need behavioural advertising data and an organisation with a published sustainability commitment that needs a reportable figure for its website emissions are not what Restate is typically brought in for.
- What can Cabin do that Restate cannot?
- Cabin covers Cookieless tracking, Carbon reporting, 1.2kb script, Custom events. Restate covers Durable execution, Virtual objects, Single binary runtime, Multi-language SDKs.
Answered from the vendors’ own pages
Cabin: Do I need a cookie consent banner with Cabin?
No. It sets no cookies and collects no cross-site identifiers, and data is stored in the EU, which is the specific reason most buyers switch to it.
Restate: Is Restate open source?
The SDKs are MIT. The runtime is under a Business Source Licence, which permits self-hosting but not offering it as a competing service.
Cabin: How accurate is the carbon measurement?
It is an estimate derived from data transfer using the CO2.js model. It is reliable for tracking change over time on your own site and unsuitable as an audited emissions figure.
Restate: How does it compare with Temporal?
Same problem, different shape: one Rust binary with embedded storage instead of a server plus database plus workers, and lower per-step latency.
Cabin: Who makes Cabin?
It was built at Normally, a research and design studio in London, out of work on data, privacy and the carbon footprint of digital products.
Restate: Is there a free tier?
Yes, fifty thousand durable actions a month on Restate Cloud with no card required.
Cabin: Can it replace Google Analytics entirely?
For traffic, referrer and event reporting, yes. For advertising attribution, audience building and funnel analysis, no.
Restate: Which languages are supported?
TypeScript, Java, Kotlin, Go, Python and Rust.
Related pages
Other head to heads
- Cabin vs DashThis
- Cabin vs Databox
- Cabin vs Google Data Studio
- Cabin vs Qlik Sense
- Cabin vs Klipfolio
- Cabin vs Heap
- Cabin vs Grow
- Cabin vs Mode
- Cabin vs Oracle Analytics Cloud
- Cabin vs Zoho Analytics
- Cabin vs Board International
- Cabin vs Fabi
- Cabin vs Segment
- Cabin vs Anaplan
- Cabin vs Domo
- Cabin vs Userpilot
- Cabin vs GoodData
- Cabin vs Hex
- Cabin vs Helix
- Cabin vs Rust
- Cabin vs Atlantis
- Cabin vs Jitsu
- Cabin vs Envoy
- Cabin vs Okteto
- Cabin vs Argo CD
- Cabin vs Steampipe
- Cabin vs Cloud Native Buildpacks
- Cabin vs Deno
- Cabin vs GitHub Desktop
- Cabin vs Istio
- Cabin vs Penpot
- Cabin vs PyCharm
- Cabin vs Sublime Text
- Cabin vs Vite
- Cabin vs Bazel
- Cabin vs Daytona
- Restate vs DashThis
- Restate vs Databox
- Restate vs Google Data Studio
- Restate vs Qlik Sense
- Restate vs Klipfolio
- Restate vs Heap
- Restate vs Grow
- Restate vs Mode
- Restate vs Oracle Analytics Cloud
- Restate vs Zoho Analytics
- Restate vs Board International
- Restate vs Fabi
- Restate vs Segment
- Restate vs Anaplan
- Restate vs Domo
- Restate vs Userpilot
- Restate vs GoodData
- Restate vs Hex
- Restate vs Helix
- Restate vs Rust
- Restate vs Atlantis
- Restate vs Jitsu
- Restate vs Envoy
- Restate vs Okteto
- Restate vs Argo CD
- Restate vs Steampipe
- Restate vs Cloud Native Buildpacks
- Restate vs Deno
- Restate vs GitHub Desktop
- Restate vs Istio
- Restate vs Penpot
- Restate vs PyCharm
- Restate vs Sublime Text
- Restate vs Vite
- Restate vs Bazel
- Restate vs Daytona
