Shared identity
Every product in the ecosystem authenticates through ALKEYON. A person signs up once and reaches every service their organization subscribes to. No separate logins, no password fatigue.
The architecture
One foundation. Every product.
Every product in the studio sits on a single infrastructure layer. Solved once, shared across everything - that is how one studio runs nine products, and how yours starts on its feet.
Shared identity
One login across every product.
Unified billing
Stripe orchestration with automatic provisioning.
Cross-product analytics
Usage, revenue and health across the portfolio.
Communication layer
Email, newsletters and notifications through one gateway.
AI integration
Model Context Protocol connecting agents to operations.
Protection and licensing
Keys, domains and activations, shared by the portfolio.
Webhook routing
Ingress, fan-out and replay. Events get where they need to go.
Storage and sync
Provider-agnostic files with tenant isolation.
Deep dive
How each layer works
Eight layers. None of them is something you will have to build.
Unified billing
Reseller runs the whole subscription lifecycle: checkout, payment, workspace creation. When a customer pays, their environment is provisioned automatically - databases, DNS, secrets, everything.
Cross-product analytics
A single analytics layer spanning every product. Track events, watch active users, measure revenue - from one dashboard, not one tool per product.
Communication layer
FF Mail delivers transactional email with automatic retry and provider failover (Resend, SendGrid, SES). FF Newsletter handles subscribers and campaigns. One infrastructure for everything that leaves the building.
AI integration
FF MCP exposes 84+ tools across the whole platform over the Model Context Protocol. Connect Claude, ChatGPT or any MCP-compatible assistant and your AI can handle billing, send email, read analytics and provision customers through conversation.
Protection and licensing
License manages software protection across every product: activation limits, domain locking, trial periods and real-time validation. One licensing system for the whole portfolio.
Webhook routing
Router receives webhooks from outside services (Stripe, GitHub and others) and fans them out to several internal destinations. Automatic retries, payload logging and one-click replay for debugging.
Storage and sync
S3-compatible storage with strict tenant isolation. Each organization gets its own namespace. Provider-agnostic: swap the backend without touching application code.
Principles
Why this architecture holds
Four rules that have not moved since the first product.
Solved once, shared everywhere
When we build authentication, we build it for every product. When we fix a billing edge case, every product benefits. The advantage compounds with each new service.
Tenant isolation by default
Every organization gets isolated databases, isolated storage, isolated secrets. Multi-tenancy is not an afterthought - it is the foundation everything else stands on.
Convention over configuration
Products follow shared conventions: how they authenticate, how they store, how they receive webhooks. Someone who knows one product already understands them all.
AI-native from the ground up
Every service is reachable through the Model Context Protocol. AI is not bolted on - it is a first-class way to operate the whole ecosystem.
This infrastructure is what we call FlowPrime - and it is available to everyone who shares the standard.