# Identity, billing and commerce for your SaaS product. > A self-hostable identity and billing platform for SaaS products, now in early access. Authiane is a self-hostable platform for user accounts, subscriptions and usage-based billing in SaaS products, now in early access. Authentication · Subscriptions & billing · API keys · Multi-tenant · Built for SaaS · Developed in Germany ## Every SaaS product needs the same account and billing work 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. ## What Authiane covers Identity, billing and commerce share one data model and one API. ### Identity User accounts, sessions and API keys for the people and the services that call your product. - Sign-up, e-mail verification, login and sessions work from the first release. - Users create their own API keys for automated calls. - Roles and permissions decide what each account may do. ### Billing Subscriptions, one-off purchases, invoices and usage-based billing with a hosted checkout. - Customers pay through a hosted checkout or with a stored payment method. - Every purchase produces an invoice with a downloadable PDF. - Usage metering enforces included allowances and bills overage. - Prepaid credit in fixed top-up amounts settles purchases and refunds instead of the payment provider. ### Commerce (Preview) Multi-tenant commerce for platforms whose tenants sell their own offers. - Each tenant manages its own catalogue, offers and staff accounts. - Tenants connect their own payment account and keep their own revenue. - Purchases, refunds and purchase history stay separated per tenant. ## Sign-in your customers and your services both use Accounts, sessions and machine credentials come from one identity service, so your product keeps no account store of its own. - E-mail sign-up with verification: A customer signs up with an e-mail address and confirms it before the first login. Unconfirmed addresses cannot sign in. - Login and sessions: The customer signs in with a password and stays signed in through a session that the platform manages and can end. - Social sign-in with GitHub: A customer can sign in with a GitHub account instead of a password. The integration is optional and is enabled per installation. - Machine credentials: Customers create API keys, and your services use service credentials of their own. Every credential carries defined scopes. - Roles and permissions per organisation: Each organisation has owners, admins and members, invites its own staff and sees only its own data. ## How a product uses Authiane 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. 1. Run the platform: Deploy Authiane in your own infrastructure, with the database and the storage of your choice. 2. Connect the product: Your frontend and your services call the platform API for accounts, subscriptions, usage and permissions. 3. Define plans and allowances: Describe what each plan includes, which usage is metered and what happens when an allowance is used up. 4. Open access to customers: Customers sign up, pay through the hosted checkout and use the product. Every permission change is logged. ## One customer, from sign-up to invoice This is the whole path a customer and your product walk once the platform is running. 1. The customer signs up: 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. 2. The customer chooses a plan: The customer picks a plan on your pricing page. The subscription for that account starts immediately, with no manual step in between. 3. The customer pays: Payment runs in a hosted checkout. The customer can save the payment method so later charges need no new entry. 4. Your product measures usage: Your product reports what the customer consumes. Included allowances are enforced, and usage beyond them is billed. 5. The invoice is ready: Every purchase produces an invoice with a downloadable PDF, and the customer sees the full purchase history of the account. ### The same path for a platform with several tenants 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. ## Who builds on Authiane The platform is built for products that sell to businesses and for the platforms that host them. - SaaS and API products: Teams that sell a subscription or a metered API and need accounts, billing and entitlements without building them. - Multi-tenant platforms (Preview): Operators whose tenants sell their own offers, keep their own revenue and manage their own staff. - Agentic commerce (Preview): Products where a software agent starts a purchase and the customer approves it out of band. ## What comes next These capabilities are planned and are not available today. They are named here so you can plan around them. - Sign-in for Azure Container Apps (Roadmap): A product that already runs there uses Authiane as its sign-in service, so its existing containerised login needs no separate account store. - Managed operation (Roadmap): Authiane runs the platform for you, including updates, instead of your team operating it. - Self-service tenant administration (Roadmap): Tenants manage their own sign-in clients, staff and permissions instead of asking the operator. ## What you can verify before you commit These are the four points a technical buyer asks about first. ### Where does Authiane run? EU hosting and GDPR: You choose where the platform runs, including the EU. [Data minimisation under Art. 5 GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng) is a design rule, and [this site loads nothing from third parties](https://www.authiane.com/privacy/). ### Who receives the revenue? Your own payment account: Each tenant connects its own payment account and receives its own revenue. Authiane never holds funds. ### Can I host Authiane myself? 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. ### Are permission changes logged? 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](https://www.authiane.com/about/), [Contact](https://www.authiane.com/contact/), [Developers and API](https://www.authiane.com/developers/) ## Join the waitlist We open early access in small groups. Leave your e-mail address and we will notify you when your turn comes. Join the waitlist: - One e-mail when access opens - Revocable at any time - No third parties Authiane is a brand of Das Digitale Momentum GmbH & Co. KG, Much, Germany. Updated: 2026-09-13 --- Source: