Inquir Compute
Deploy from a GitHub repository, a Dockerfile or a container image. Bring APIs, websites, workers and databases into one project.
npm i -g @inquir/compute-cliCONTAINER APPLICATIONS
01 / Deployment
Set the container image, port and health check. Follow each release through startup and open its logs directly from your project.
The API is running with private access.
02 / Private networking
Add PostgreSQL from a template with persistent storage. Insert its connection into the API variables, then redeploy to apply DATABASE_URL.
Connection configured. Both services remain private.
03 / Replicas
Increase replicas for a service without local storage. The platform starts additional containers and routes traffic to ready replicas.
Three API replicas. One database.
04 / Observability
Select a service and read deployment events alongside its current container’s logs. Check startup with the context of the project still in view.
The API is healthy. Its event and log line stay together.
THE OLD WAY
Or — just deploy the container.
What you get
Everything a container needs to be a service — build, release, route, persist, connect — done by the platform, with the same controls whether it is a Dockerfile you wrote or an image you pulled.
Every deploy is an immutable image digest started next to the running one. It serves only after your own health check passes — on a preview URL first. Promote it when you are ready, or let it promote itself the moment it is healthy.
Promotion keeps the previous release as the rollback reserve, so going back is a pointer flip, not a rebuild. A release that fails shows the reason and the next step instead of a spinner.
Every application gets a permanent <slug>.apps.internal address that only its workspace can reach. Public domains are opt-in. Connect a database to a service and the connection URL lands in its variables.
Postgres and Redis from a template, with a persistent volume, a private TCP endpoint and a connection URL. Any container can mount named volumes; they are snapshotted every 6 hours and restorable on demand.
Bind your own hostname, prove it with a TXT record, and the platform routes it with an automatic certificate. WebSockets and server-sent events pass straight through the proxy.
Build and release with inquir apps deploy, stream logs, open a shell into a running release from the dashboard, keep production-only variables out of previews. Health check, replicas, memory and CPU are release settings, not YAML.
How it works
No cluster, no YAML, no ingress controller — a container, one command, a URL.
Any base image, any language. The platform builds it on its own builders and pins the result to an immutable digest — or skip the build and release an image you already have.
FROM node:22-alpine WORKDIR /app COPY package*.json ./ RUN npm ci --omit=dev COPY . . EXPOSE 3000 CMD ["node", "server.js"]
inquir apps deploy snapshots the source, builds the image, starts a release next to the running one and waits for your health check. The release gets a preview URL of its own.
$ inquir apps create web --port 3000 $ inquir apps deploy web ✓ Image built · digest pinned 41s ✓ Health check passed 2.1s → https://web-a1.preview.apps.inquir.org
Promote points production at the healthy release and keeps the old one as the rollback reserve. Connect a database, and its URL appears in the service’s variables over the private network.
$ inquir apps promote r-8f2c ✓ Production → web-a1.apps.inquir.org $ inquir apps connect db web ✓ DATABASE_URL → db-a1.apps.internal:5432 $ inquir apps rollback web ✓ Production → r-71aa, instantly
The build runs on the platform, the release starts next to the one that is serving, and traffic moves only after the health check says so.
FROM node:22-alpine WORKDIR /app COPY package*.json ./ RUN npm ci --omit=dev COPY . . EXPOSE 3000 CMD ["node", "server.js"]
Source snapshot · 1.8 MB · sha256:3f9c…
Image built on the platform builders · 41s
Release r-8f2c started next to r-71aa
Health check GET /healthz passed · 2.1s
Preview live — promote when readyhttps://web-a1.preview.apps.inquir.orgDatabases, private networking, custom domains and the HTTP API — from the same CLI you deployed with. These are the examples from the docs.
# 1. Create the application — an HTTP service listening on port 3000 inquir apps create web --port 3000 # 2. Deploy: builds the Dockerfile in the current directory, releases the image # and waits until the health check passes. The release gets a preview URL. inquir apps deploy web # …or release a prebuilt image instead of building inquir apps deploy web --image nginx:alpine # 3. Promote: production traffic moves to this release (owner/admin login) inquir apps promote <releaseId> inquir apps status web # endpoints, hostnames, recent releases inquir apps logs web --tail 100 # stream container logs inquir apps rollback web # back to the previous production release
One platform
Run your core service in a container and add serverless functions for webhooks. Use pipelines to run those functions on a schedule or connect them into work with multiple steps.
Deploy an API, website or worker from a Dockerfile or image. Connect a database over the private network, add replicas and roll back a release when you need to.
Deploy a container applicationRun Node.js, Python or Go code on an HTTP request, webhook or pipeline step. Build API handlers, integrations and background tasks without keeping a dedicated service running.
Explore serverless LambdasRun function calls on a schedule or connect them into workflows with multiple steps. Add branches and retries, and follow each step from its input to its result.
Build a pipelineUse cases
Long-lived processes that never fit a function — with the deploy flow of one.
A Next.js, Rails or Django service next to a Postgres from a template: the private connection URL in its variables, a custom domain in front, a preview URL per release, rollback when a migration goes wrong.
A long-running agent or tool server with WebSockets and streaming, a Redis for memory next to it, secrets scoped to production — and the functions and pipelines that call it, in the same workspace.
Postgres, Redis, SMTP relays, SSH bastions, message brokers: raw TCP ports, private by default, public with a stable endpoint port when you say so. Snapshotted every 6 hours.
Pricing
From your first deployment to a growing product: free beta access, two paid plans and individual Enterprise terms.
Try Inquir with your first project. Deploy an application or run a function for free during beta.
No credit card required
For personal projects and small products ready for their next step.
View current pricing and included resources in your account.
For developers and teams growing their production workloads.
View current pricing and included resources in your account.
For organizations with specific resource, deployment and support requirements.
Free access is available during beta. Paid plan prices and limits follow the current catalog; Enterprise terms are agreed individually.
FAQ
Hi, it's the Inquir Compute team. Ask AI about container apps on Inquir:
Free during beta. No YAML. No cluster.