Identity
Shared authentication and authorization — one login, one set of users and roles, strict multi-tenancy.
DIN 0815/S · PLATFORM SERVICES
Eleven shared backend services. Reusable capabilities the modules consume over APIs — never the other way around.
Platform Services are shared backend capabilities — each does one cross-cutting job and exposes it over an API. A module may depend on several; a service never depends on a module. All ship MIT-licensed with full source code.
Shared authentication and authorization — one login, one set of users and roles, strict multi-tenancy.
Automation for all modules — workflows, triggers, events, scheduling, and reliable outbound webhooks.
Centralized notification delivery across email, SMS, push and chat, with templates and a retryable queue.
Shared AI capabilities — chat, embeddings, RAG and prompt management behind one provider-agnostic API.
Centralized third-party integrations — encrypted connections, a REST/GraphQL proxy, and verified webhooks.
Shared blob store — buckets, content-addressed objects, and short-lived signed download links.
Tamper-evident, append-only activity trail — who did what to which resource, verifiable end to end.
Take and reconcile money — payment intents, refunds, an append-only ledger and verified PSP webhooks.
Cross-entity keyword and faceted search over every module’s records, on SQLite FTS5.
One authority for gapless sequence numbers — invoice numbers, order refs, offer numbers, PO refs.
The party master record — one answer to “who is this customer?” across every module in a stack.
Dependencies point strictly downward. Business Modules are customer-facing applications; Platform Services are the reusable backend capabilities they compose. Services may depend on each other and on infrastructure — never on a module.
Browse modules →