What is this website?
tiun is a unified backend for AI and SaaS products: authentication, payments and billing, a customer database, and analytics in one system. It aims to cut the cost of wiring separate auth, payments, and reconciliation stacks, and offers MCP/skills-style integration so developers or agents can help with setup.
Core Features
- Ready auth flows: sign-up/login/logout, profile components, plus SMS, email, and social SSO multifactor options.
- Payments and billing for one-time, subscription, usage, and time-based pricing; checkout components; Merchant of Record handling for tax and dispute-related operations.
- A customer database that keeps users, transactions, and sessions together so subscription status stays aligned with profiles.
- Session/event tracking, transactional email, invoice history, and self-serve plan changes.
- Analytics and exports, with optional AI-native analytics on the pricing page, plus SDK/MCP entry points.
Common Use Cases
- Indie builders or small teams shipping an AI/SaaS product with login and paid plans without assembling several vendors and webhook glue first.
- Products that need usage billing or self-serve upgrades/downgrades while keeping payment state consistent with customer records.
- Product/growth teams that want signups, payments, and usage on one data model instead of reconciling across tools.
- Engineering teams that prefer MCP/skills so an agent can assist with integration work.
Who is it for?
- SaaS/AI startups and solo developers who value Europe hosting and GDPR-oriented positioning.
- Small teams consolidating auth + payments + customer DB to reduce sync logic.
- Poor fit: orgs locked into a custom payment stack, needing only one narrow capability, or with hard hosting-region conflicts.
- Also a weak fit if you expect zero transaction fees or refuse MoR/fee structures while still outsourcing payment compliance.
How does it compare to similar tools?
Useful decision checks:
- Scope: payments-only versus auth + payments + customer data + analytics together.
- Commercial model: platform subscription versus transaction fees plus optional add-ons.
- Integration style: classic SDK/webhooks versus additional MCP/skills for agents.
- Hosting/compliance: whether Europe hosting and GDPR claims match your launch constraints.
What Our Customers Say
Builders often say login and billing ship faster when webhook and sync work shrinks; some teams use it to try usage-based pricing. If you already run a mature custom payments and identity stack, migration cost can outweigh the benefit.
FAQ
Q: How is tiun different from payments-only tools?
A: It frames auth, payments, customer records, and analytics as one backend—not just a checkout link or payment API.
Q: Is there a free plan?
A: Pricing lists Free and Enterprise. Free covers core platform capability with transaction fees; paid analytics add-ons and enterprise options are listed separately.
Q: Who is the primary audience?
A: Official positioning targets AI and SaaS builders via Web/API/SDK/MCP—not a consumer app-store product.
