Early access
Authiane is a self-hostable platform for user accounts, subscriptions and usage-based billing in SaaS products, now in early access.
The starting point
A SaaS product needs user accounts, sessions, API keys, subscriptions, invoices and usage limits. These functions are almost the same in every product, and they still have to be built, tested and maintained each time. Authiane provides them as one platform that you run in your own infrastructure, so this work is done once.
The platform
Identity, billing and commerce share one data model and one API.
User accounts, sessions and API keys for the people and the services that call your product.
Subscriptions, one-off purchases, invoices and usage-based billing with a hosted checkout.
Multi-tenant commerce for platforms whose tenants sell their own offers.
One data model · one API
Authentication
Accounts, sessions and machine credentials come from one identity service, so your product keeps no account store of its own.
A customer signs up with an e-mail address and confirms it before the first login. Unconfirmed addresses cannot sign in.
The customer signs in with a password and stays signed in through a session that the platform manages and can end.
A customer can sign in with a GitHub account instead of a password. The integration is optional and is enabled per installation.
Customers create API keys, and your services use service credentials of their own. Every credential carries defined scopes.
Each organisation has owners, admins and members, invites its own staff and sees only its own data.
How it works
Authiane sits in front of the product as one public boundary and answers every request that needs an account, a subscription or a permission.
The product receives the caller's identity and permissions from Authiane and implements only its own business logic.
Deploy Authiane in your own infrastructure, with the database and the storage of your choice.
Your frontend and your services call the platform API for accounts, subscriptions, usage and permissions.
Describe what each plan includes, which usage is metered and what happens when an allowance is used up.
Customers sign up, pay through the hosted checkout and use the product. Every permission change is logged.
Worked example
This is the whole path a customer and your product walk once the platform is running.
The customer enters an e-mail address, confirms it and has an account. You keep no account store and send no confirmation mail of your own.
The customer picks a plan on your pricing page. The subscription for that account starts immediately, with no manual step in between.
Payment runs in a hosted checkout. The customer can save the payment method so later charges need no new entry.
Your product reports what the customer consumes. Included allowances are enforced, and usage beyond them is billed.
Every purchase produces an invoice with a downloadable PDF, and the customer sees the full purchase history of the account.
A platform hosts several tenants on one installation. Each tenant connects its own payment account and keeps its own revenue. A customer keeps one account and can buy from more than one tenant, while staff accounts, offers and purchase history stay separated per tenant.
None of this is work you build: no account store, no checkout, no invoice generation, no usage ledger.
Use cases
The platform is built for products that sell to businesses and for the platforms that host them.
Teams that sell a subscription or a metered API and need accounts, billing and entitlements without building them.
Operators whose tenants sell their own offers, keep their own revenue and manage their own staff.
Products where a software agent starts a purchase and the customer approves it out of band.
Roadmap
These capabilities are planned and are not available today. They are named here so you can plan around them.
Today: early access
A product that already runs there uses Authiane as its sign-in service, so its existing containerised login needs no separate account store.
Authiane runs the platform for you, including updates, instead of your team operating it.
Tenants manage their own sign-in clients, staff and permissions instead of asking the operator.
Trust
These are the four points a technical buyer asks about first.
EU hosting and GDPR
You choose where the platform runs, including the EU. Data minimisation under Art. 5 GDPR is a design rule, and this site loads nothing from third parties.
Your own payment account
Each tenant connects its own payment account and receives its own revenue. Authiane never holds funds.
Self-hostable now, managed later
Yes, in early access: each team runs the platform in its own infrastructure. A managed operation is on the roadmap.
Logged permission changes
Every change to roles, API keys and permissions is recorded in an audit log.
More about the operator and the API: About Authiane · Contact · Developers and API
Early access
We open early access in small groups. Leave your e-mail address and we will notify you when your turn comes.