Evidence
Every capability below is read from a typed inventory that Alodai keeps in its own repository. Each card says what it promises, how far it has got, who can use it, and what it does not do.
The evidence law
Built means the code exists and its automated tests pass. Tested means someone ran it on a real stack and wrote the run down. Proven means that written run carries a date.
None of that means live for the public. A recorded run is a record of a test, not an observation of production. This page never shows a capability as live, and a planned capability is never shown as available.
Status is worked out from the evidence, not written by hand. When a limitation could change a buying decision, it sits on the card next to the promise.
Legend
Organization
Organizations own units, delivery projects and brands, with inherited Console role bindings for scoped human access.
What it does not do
Coordinate formation, corporate documents, obligations and qualified provider handoffs around an organization’s context.
What it does not do
Business
Checkout code for Alodai billing its own organisations and for paid course enrolment on a platform, with money held as integer cents.
What it does not do
A PDF with a text layer is extracted by a model into typed fields, and a person reviews and approves them in a cockpit with an append-only log.
What it does not do
Recurring class schedules, member bookings with a capacity guard, a first-come waitlist that promotes on cancellation, and a manager roster.
What it does not do
A published site's form captures an enquiry into the platform's Admin Panel, where it is read, starred, archived, answered or erased.
What it does not do
Maintain platform-scoped contacts, companies and leads for business work.
What it does not do
Manage explicit fiscal issuers and commercial document transitions, with project economics and expense records.
What it does not do
Track platform projects, milestones, tasks, relations and workforce records through scoped modules.
What it does not do
Digital
An authenticated app for each customer platform, created and configured in the Console, served from one image at its own subdomain or a custom domain.
What it does not do
A written brief compiles, in staged and resumable passes, into a draft platform and site that a person reviews before anything goes live.
What it does not do
Capabilities are switched on per platform from one registry, and a module marked as not yet built cannot be enabled for a platform — the core service refuses it.
What it does not do
A pack configures a platform for a vertical — modules, copy, navigation and seed content — without owning any data.
What it does not do
A public site assembled from governed blocks and published at a site subdomain or a custom domain, with no app to deploy.
What it does not do
Uploaded files stored as private objects under stable keys and served through URLs signed at read time, with public assets for published sites.
What it does not do
A travel experience on a customer platform: a map of expeditions, a narrated guide, questions at each stop and a passport of places visited.
What it does not do
Install code-shipped platform capabilities through registered manifests and platform configuration.
What it does not do
AI
Four model providers behind one router, a spend guard in front of every call, and bring-your-own keys at organisation and platform level.
What it does not do
COS proposes bounded business actions through an allowlisted kernel and approval ledger; Cortex separately recommends engineering run plans without executing them.
What it does not do
Cloud
The estate runs on Alodai-operated servers in Europe: Docker Swarm behind Traefik with automatic TLS, data on its own host, monitoring, alerting and off-site backups.
What it does not do
A control plane that lets an operator see and change the estate — domains, services and hosts — from one governed surface.
What it does not do
Shared foundations
One account for the people who use Alodai-built platforms, and one click from the launcher into a platform, already signed in.
What it does not do
Sign-in, sessions and roles for every platform, with each request checked against its tenant in the service code before it touches a row.
What it does not do
Claims about system state recorded with their evidence, source tier, freshness and confidence, with standing derived rather than stamped.
What it does not do
Account and product email rendered from stored templates with per-platform branding and sent through a queue.
What it does not do
An organisation installs Alodai's GitHub App and links repositories, whose activity is read into the platform on request.
What it does not do
Public product documentation at docs.alodai.com, readable by anyone without an account.
What it does not do
Record operator delegations, reviews, decisions and outcomes, with advisory enrichment of persisted redacted transcripts.
What it does not do
One governed view across the organization: what matters now, what changed, who owns it, what needs approval, what evidence supports it and what happens next.
What it does not do
Dispatch configured integration events through provider adapters and queued delivery.
What it does not do
Evidence · next step
Tell us what you need to run. We will tell you which of these is real today and which is not.