Private beta
Cuitty is rolling out product-by-product. Here's how it works and where each product stands.
What private beta means
Cuitty is in private beta. Every product, plugin, and module goes through a staged rollout:
- Internal dogfooding — we use it ourselves and fix what breaks.
- Private beta (invited orgs) — selected teams get access, provide feedback, and help shape the product. This is where most products are now.
- Open beta — broader access, but still evolving. API stability guarantees begin.
- General availability — stable, documented, supported with SLAs.
During private beta, Cuitty is fully functional — demos on this site use production data shapes, the docs are complete, and beta orgs run real workloads. The beta label reflects our commitment to shipping only what we're confident in, not a lack of capability.
Per-tier status summary
35 entries across the ecosystem. 30 in private beta, 5 in preview.
How invitations are sequenced
We sequence invitations to ensure every beta org gets attention and support. Priority is based on:
- Product fit — teams whose use cases align with the products they requested.
- Feedback capacity — teams willing to provide technical feedback and collaborate on shaping the product.
- Infrastructure diversity — we deliberately invite teams across different cloud providers, stack choices, and scales to stress-test broadly.
- Request order — among equivalent candidates, earlier requests are prioritized.
When your org is invited, you receive a dedicated onboarding session and a direct channel to the engineering team. Beta access includes all currently live products — you pick which ones to activate.
We expand the beta cohort regularly as capacity and confidence grow. Requesting access is non-binding, and you can specify which products matter most to you.
Explore the private beta
Browse the available products and learn how each one is rolling out.