1. Product path
Normal customers should use self-serve signup.
Create a workspace, confirm the email flow if needed, and manage credits, requests, and API keys from the dashboard.
Private beta
Keep the beta loop
tight and useful.
Runtime is meant to feel like a normal SaaS product. This page is just for private-beta teams who want early access, faster feedback, or launch updates while the self-serve path matures.
Beta summary
Real product first.
Beta access second.
The private beta should help us polish onboarding, dashboard flows, and API key setup. It should not become a second auth model or a separate internal console.
2. Beta access
This page is only for the private beta loop.
Use it when you want early feedback, launch updates, or a tighter back-and-forth while the product is still settling.
3. Why join
Shape the product without learning weird internal flows.
The goal is to harden the normal SaaS path, not to make people memorize internal tools, tenant IDs, or pasted tokens.
Fit check
Who should join the beta
and who can just sign up now.
Good fit
You already run AI traffic and want to pressure-test the self-serve product before a broader rollout.
Good fit
You care about pricing clarity, request visibility, and machine-key setup staying simple for real teams.
Later
You mainly want a one-off sales process instead of using the product directly.
Later
You are not ready to run real traffic through the gateway yet.
Join the loop
Want beta updates,
feedback sessions, or early access?
Use this form if you want to be part of the private beta. For normal product use, just create a workspace and stay on the self-serve dashboard path.