Deployment & observability
The platform ships as a set of containers on PostgreSQL, Redis and Kafka — designed to run in tiers, so you're not forced to stand up the full stack just to develop against it.
Tiered footprint
A lean core tier is enough for local development. A full platform tier adds every service a real product needs. An observability tier layers on distributed tracing, metrics and log aggregation — useful once you're running something you actually need to operate, not just build.
Self-hosted or managed
Run it on your own infrastructure — your cloud account, your region, your network boundary — or have MergeMind run it for you. Dedicated, VPC and on-premise deployment are part of the Dedicated Enterprise engagement for teams with infrastructure or governance requirements that rule out shared hosting.
What you can actually see at runtime
Distributed request tracing, metrics and structured logs are wired into every service from day one — not added after the fact when something breaks in production and no one can tell why. When something is slow or failing, you can see the request's path across services, not just a single service's logs in isolation.
What's implemented today versus what's still on the roadmap — including formal data-residency and backup/DR commitments — is stated plainly on Security & Trust, not glossed over.