What it does
Inquir Compute deploys applications from a Dockerfile or a container image. A project can hold APIs, websites, background workers and databases. The command inquir apps deploy builds the image on the platform builders and pins its digest. The new release starts next to the running one and gets its own preview URL. The platform waits for the health check to pass before the release serves traffic. Promoting points production at the healthy release. The previous release stays as the rollback reserve. Postgres and Redis can be added from templates. The connection URL then appears in the service variables over the private network. Functions run Node.js, Python or Go code on an HTTP request, a webhook or a pipeline step.
Capabilities
- Inquir Compute says a release that fails its health check never receives traffic, and production keeps serving the previous release.
- Every application gets a permanent address in the form <slug>.apps.internal that only its workspace can reach, and public domains are opt-in.
- Named volumes are backed up automatically every 6 hours today, but applications whose volumes hold more than 2 GB in total are not included in platform backups yet.
- Custom domains are verified with a TXT record and routed with an automatic TLS certificate.
- Inquir Compute says its CLI is an MCP server that lets an agent deploy, read logs and roll back a release.
When to use it
- You want to run a web app next to its Postgres database, with a custom domain, a preview URL per release and rollback.
- You want to host a long-running AI agent with WebSockets and streaming, and a Redis instance for its memory.
- You want to host a Telegram or MAX bot with Postgres and Redis beside it.
