Developers
Build on Maevu: an API-first core, connectors as a language, and self-hosting.
Alpha. APIs are stabilising. Expect change, and expect us to tell you about it.
API-first, all the way down
Maevu is a set of engines with an API in front — triage, scheduling, rules, traceability. Every screen is just a representation of that API. Anything the product can do, you can do over the API, because the product uses the same contract you do.
Connectors as a language
Connectors extend Maevu — pulling in tasks, calendars, storage, notes — and they’re written in a small, safe language (the Maevu DSL) rather than a general-purpose plugin SDK. A connector describes what should happen as pure rules; it can’t reach beyond the capabilities it’s granted, and what it’s allowed to touch is disclosed and consented at install.
The point is reach: a connector should be something a delivery lead can read and adjust, not only a programmer. We’ll publish the language reference as the alpha opens.
Extending safely
- Object-capability model — a connector reaches only its declared allowlist and granted capabilities. No ambient access.
- Trust tiers — first-party, verified, and community connectors, with signed manifests.
- Marketplace (roadmap) — install connectors like apps; register your own with a client id and secret.
Self-hosting
The core is open (AGPL) and self-hostable. Smaller teams can use our multi-tenant cloud; larger teams can run a single-tenant instance or host it entirely themselves. Packaging and images land as we approach general availability — see the roadmap.