Civimatica Model as a service
Run Civimatica models on your own systems.
Simple access means we operate the experience and you consume results through the API. Model as a service is for teams who need the models themselves — delivered as artifacts you run on your own infrastructure, applied to your own products or operations.
What you get
- Model artifacts versioned like the API (
2026.09-style releases). - The same street-state output schema the API returns, so your downstream systems do not change between hosted and self-run modes.
- Update channel: new releases ship on a cadence you choose, and you decide when to adopt them.
You keep control of where models run — your cloud, your servers, your edge fleet — and how they are applied to your use cases.
Running modes
| Mode | Where it runs | Input | Output |
|---|---|---|---|
| Hosted (API) | Civimatica | Device measurements | Street state via API |
| Self-run (MaaS) | Your systems | Your sensors or ours | Street state in your pipeline |
| On-device | Edge devices | Local sensing | Results at the edge |
Self-run accepts either measurements from Civimatica devices or compatible sensor inputs you own — the interface is the same structured observation format.
Example
A city's traffic team runs our models on their own systems for their own use cases — monitoring corridors and planning responses — without sending their data outside their environment.
Getting set up
Model-as-a-service is provisioned per organisation. Email hello@civimatica.com with your target environment and use case.