Appearance
Installation Preview
v1 preview
There is no supported public self-hosted installation during beta. The repository and production Compose release will become public under AGPLv3 when Managani reaches v1. Do not copy deployment commands from private development environments or old drafts.
Planned Deployment Shape
The v1 installation is intended to provide a documented Docker Compose deployment with these services:
| Service | Purpose |
|---|---|
| Managani App | Main web application and API |
| WebSocket | Realtime updates |
| MCP Server | Model Context Protocol interface |
| MongoDB | Product and account data |
| Memcached | Distributed cache |
| Typesense | Full-text and vector search |
Production deployments will also require a public HTTPS origin, SMTP delivery, secrets management, durable storage, backups, monitoring, and any configured AI-provider credentials.
Release Gates
Before the installation guide becomes executable, v1 must provide:
- A public repository with the AGPLv3 license attached to the complete application.
- A versioned production Compose file and supported service versions.
- A complete configuration reference with safe secret handling.
- Tested initialization, health checks, upgrades, backups, and recovery.
- Public release notes and a documented support boundary.
During Beta
Use Managani Cloud for the supported product. If self-hosting is a purchasing requirement, send the infrastructure, data-location, security, and operational requirements with your beta-access request so they can inform the v1 documentation.
Continue to the configuration preview for the planned service boundaries.
Prepare Questions for the v1 Release
Before selecting infrastructure, list the public domains, mail delivery requirements, attachment storage needs, and backup responsibilities for your intended installation. Identify the team that would maintain those services and respond if a customer-facing surface becomes unavailable.
Review the configuration preview to understand the planned boundaries between the application, search, cache, and AI providers. Keep deployment credentials out of planning documents. Once v1 is released, compare your assumptions with the supported versions and installation instructions before provisioning production services.
A service starting successfully is only one part of installation verification. The final procedure must also establish that sign-in, realtime updates, search, email, and customer-facing widget behavior work together.