Start with one focused service or compose a complete backend foundation. Every module states its readiness, dependencies, interfaces, deployment path, and commercial basis before you evaluate it.
Prefer to explore alone? Open the evaluation sandbox.
01 / Enterprise Foundation
A coordinated B2B SaaS foundation for company identity, authorization, entitlements, notifications, auditability, and day-to-day administration. AWS is the first supported deployment path; GCP remains explicitly planned.
What stays consistent
02 / Complete catalog
01
Company identity, authorization decisions, auditability, and customer API access boundaries.
Organizations, users, teams, invitations, and tenant-aware identity primitives for B2B SaaS.
Commercial model: Perpetual source license.
Central policy decisions for tenant, role, and resource-level permissions across services.
Commercial model: Perpetual source license.
A chronological event trail for product operations, investigations, and customer-visible history.
Commercial model: Perpetual source license.
Scoped customer credentials, rotation, revocation, and usage boundaries for product APIs.
Commercial model: Not yet available.
02
Product plans, feature access, usage enforcement, and the billing integrations around them.
Plans, features, usage counters, and runtime checks for what each company can access.
Commercial model: Perpetual source license.
A potential integration layer for mature billing providers; development is demand-gated.
Commercial model: Not yet available.
03
Reusable operational workflows for messages, files, forms, scheduling, and internal teams.
Tenant-aware routing, templates, scheduling, and retries for email, SMS, push, and webhooks.
Commercial model: Perpetual source license.
Multi-tenant conversations, realtime messaging, moderation, and composable React and Flutter UI kits.
Commercial model: Design-partner pilot terms.
Upload, metadata, storage-provider, and delivery workflows for customer-owned object storage.
Commercial model: Perpetual source license.
Dynamic forms, file-backed submissions, and an assignment-ready operational inbox.
Commercial model: Perpetual source license.
Working hours, resource availability, reservations, and collision-aware scheduling workflows.
Commercial model: Design-partner pilot terms.
04
Local tooling, infrastructure artifacts, service scaffolding, and an integrated operator interface.
An operator interface wired to the Foundation services for common support and administration tasks.
Commercial model: Design-partner pilot terms.
A Go service baseline that follows the same configuration, transport, logging, and deployment conventions.
Commercial model: Design-partner pilot terms.
Customer-owned infrastructure artifacts for the supported AWS deployment path.
Commercial model: Design-partner pilot terms.
Local service orchestration intended to simplify repeatable development environments.
Commercial model: Not yet available.
Runtime translation and string-template orchestration on the product roadmap.
Commercial model: Not yet available.
Choose with confidence
