Full access to SSO and managed RADIUS before billing becomes relevant.
Pricing
Start free. Upgrade only when the team actually grows.
AuthBeast is designed for early-stage teams that want a real identity and network access layer before they are ready for enterprise billing. Create the tenant first, use the product, and move to a paid plan only after you need more than 16 users.
When your tenant grows past 16 users, that is when the upgrade flow matters.
Plans
Pricing that matches the adoption path
The public site should help users start. Billing belongs after the tenant exists, not before it.
Launch the tenant
Free
Best for startups proving identity, SSO, Wi-Fi, and VPN access inside one control plane.
- Up to 16 users included
- Hosted directory, SAML SSO, and managed RADIUS
- No separate checkout step on the marketing site
Start free
Recommended first step for every new tenant.
Grow past the free limit
24 EUR / month
For teams that outgrow 16 users and want to lock in the early rate while they scale.
- Up to 128 users
- Best fit once your tenant already has real usage
- Upgrade from inside the console when you need it
Create tenant first
The upgrade should happen after tenant creation, not before.
Run AuthBeast broadly
60 EUR / month
For teams using AuthBeast as a more central part of their access infrastructure.
- Unlimited users under fair use
- Better fit once identity and network access are operational dependencies
- Managed from the tenant billing flow
Start on free tier
Most teams should not buy this before they have a live tenant.
Best flow
How billing should work
This keeps the product easier to adopt and keeps Stripe tied to a real tenant, which matches how the backend already models billing.
Create the tenant
Admins sign up, create the company tenant, and get to a usable console immediately.
Use the free seat allowance
Add users, connect apps, and roll out Wi-Fi or VPN access without introducing billing friction on day one.
Upgrade inside the console
When the tenant exceeds 16 users, prompt for upgrade from the product billing flow instead of a public checkout button.
Questions
What users usually want to know first
Answer the adoption questions directly so pricing reinforces trust instead of pushing checkout too early.
Do I need to pay before trying the product?
No. The intended path is to create a tenant, use the free 16-user tier, and only deal with billing when the team outgrows it.
Why not buy the paid plan from the landing page?
Because billing is tied to a tenant. The cleaner flow is signup first, then upgrade from the console where the tenant and usage already exist.
When does the Early Adopter plan make sense?
After you know the tenant is live and the free tier is no longer enough. It is an upgrade path, not the first interaction.
What should the CTA be on this page?
Always a signup-first CTA. The public site should optimize for tenant creation and first usage, not checkout.
Start now
Open the tenant and let billing happen later.
That is the simplest story for users and the cleanest fit with how AuthBeast already handles subscriptions and billing in-product.