MetaLoom Studio · commercial edition
MetaLoom stays open source and stays on your hardware. Studio is what you add when the archive stops being a side project — identity, storage, cleared model licenses, and someone whose job it is to answer.
In development alongside 1.0.0 — nothing is for sale yet
Open core, in writing
The platform — server, engine, every processing node, the API, the UI — is Apache 2.0 and stays that way. Studio adds the things that only exist because a company is on the other end of them: agreements, credentials, licenses, an answer.
A capability that has shipped open source stays open source. Studio is additive — this page is the record, and it is dated.
Studio does not count your minutes, frames or assets. You bought the hardware; run it until it melts.
A Studio install works with no route to us. Entitlement is a file you hold, not a service you depend on.
Access
Studio wires MetaLoom into the identity provider you run: OIDC and SAML single sign-on, directory groups mapped onto MetaLoom roles, accounts provisioned and — the part that matters at an audit — de-provisioned automatically.
Storage
Point Studio at S3-compatible object storage — MinIO, Ceph, a rack of your own or a provider you already pay — and let cold material fall through to cheap tiers while the index stays instant. Multi-site installs replicate only what they need.
Licensing
Two of MetaLoom's strongest defaults are non-commercial: the InspireFace packs behind face recognition and Ideogram 4.0 behind image generation. Studio ships a cleared bundle — checked, pinned, versioned and named in your agreement — so the legal question is answered before the pipeline runs, not after a client asks.
Operations
Signed images with an SBOM, a supported Helm chart, an LTS line that gets security fixes without feature churn, backup and restore that has been rehearsed against a real archive, and dashboards that were not drawn during the incident.
Support
A support agreement with response times written into it, an engineer who has already seen your topology, and a hand on the migration from the demo container to the rack. Roadmap conversations go both ways — Studio customers are why features get ordered the way they do.
Fit
Every real pipeline hits one step that is specific to the house: a legacy MAM, a delivery spec, a codec nobody else has, a naming convention from 2009. Studio covers custom nodes and connectors as part of the engagement — kept working across upgrades instead of rotting in a fork.
Where the line is
Community is the whole platform and always will be. Studio is the same software with the organisational parts attached.
| Capability | Community Apache 2.0 · free, forever | Studio Commercial · pricing with 1.0.0 |
|---|---|---|
| Loom server, Cortex engine, all 19 node kinds | included | included |
| Self-hosted, unmetered, air-gap capable | included | included |
| REST · GraphQL · CLI · web & desktop UI | included | included |
| Pipeline editor, chat agent, skills & memory | included | included |
| Community support — Discord and the issue tracker | included | included |
| SSO (OIDC / SAML), SCIM provisioning, audit trail | not included | included |
| S3-compatible object storage, tiering, multi-site | not included | included |
| Commercially cleared model bundle + indemnity | not included | included |
| Signed builds, SBOM and a maintained LTS line | not included | included |
| Support agreement with written response times | not included | included |
| Custom nodes, connectors and OEM terms | not included | included |
No feature has ever moved from the left column to the right one, and none will.
Who Studio is for
Early access
Nothing is for sale yet and there is no price list to show you. What exists is a roadmap and a short list of people whose problems are shaping it. If the page above described your situation, say so — that is the whole application process.
An email reaches a person, not a funnel. There is no mailing list to add you to yet, so nothing happens to your address except a reply.
