Deployment options¶
Hosted — api.venkai.fr¶
Beta
The default. Nothing to install, operate or upgrade: create an API key and call the API. Everything in this documentation applies to it directly.
| Endpoint | https://api.venkai.fr |
| Dashboard | app.venkai.fr |
| Isolation | Per organization, on every request |
| Upgrades | Continuous. Venkai is pre-1.0 — see Status & maturity |
| Your responsibilities | Keys, client-side failure handling, optional exports — see the Production checklist |
Private deployment¶
Beta
For teams whose data must stay inside their own infrastructure, Venkai can run
as a private deployment. It exposes the same API as the hosted service, so
an integration built against api.venkai.fr works by changing
VENKAI_BASE_URL.
Private deployments are set up together with the Venkai team. Operator documentation — installation, configuration, backups, upgrades and rollback — is provided as part of that engagement.
What you need to provide¶
| Requirement | Notes |
|---|---|
| A container runtime | A single host is enough to start |
| A managed or self-operated database | Supported engines are specified in the operator documentation; your backup and retention policy applies |
| A domain and TLS termination | For the API and the dashboard |
| Outbound internet at install time | Not required at runtime: retrieval does not call external services |
What you own¶
| Area | Responsibility |
|---|---|
| Infrastructure, network, TLS | You |
| Database backups and restore tests | You |
| Secrets management | You |
| Applying Venkai releases | You, with release notes and upgrade steps from Venkai |
| Software defects and upgrade path | Venkai |
To discuss a private deployment, contact us via venkai.fr.