On this page
Kilby documentation
Kilby runs your web services, private services, background workers and cron jobs from a container image or from a Git repository that it builds, and managed Postgres databases. Each workspace has its own namespace, network rules and resource quota, which keeps workspaces apart; customers still share machines, and Security and isolation says what is covered and what is not. Everything you can do in the dashboard you can also do over a REST API with an OpenAPI description, so a script or an AI agent can deploy and operate Kilby too.
Kilby is in beta. It is free during the beta: nothing is billed today.
What you can run#
- Web services with a public HTTPS address, and your own domain with a certificate that Kilby issues and renews.
- Private services that only your other services can reach: a model server, a vector store, a cache.
- Background workers for queues and agents, and cron jobs that run on a schedule.
- Templates: ready-made open-source AI apps, vector databases and tools (17 of them), each deployed from one page.
- Managed Postgres (17 and 18) with pgvector enabled, continuous backups and point-in-time restore, and a managed Redis-compatible Key Value store.
- Environment groups: variables defined once and shared by many services.
- Projects and environments: group what you run, for example into Production and Staging. This organizes; it does not isolate.
- Persistent disks, several instances, autoscaling, health checks, rollbacks, logs, metrics and a shell.
- Kilby AI, which explains a failed deploy in plain English and proposes a fix, in the workspaces that turn it on.
You can deploy a container image, public or private, or a Git repository from GitHub, or a public repository from github.com, gitlab.com and bitbucket.org by its address. See Deploy from Git.
Start here#
- Quickstart: deploy a public image in two minutes.
- Templates: deploy a ready-made app instead.
- Use Kilby from an AI agent: the API, the OpenAPI document, the MCP server and the safety model.
- Services: web, private, worker and cron, and what each instance type costs.
- Troubleshooting: why a deploy fails and what to change.
All pages#
Get started#
- Quickstart: Create an account and run a public container image at an HTTPS address in about two minutes.
- Templates: Deploy a ready-made open-source AI app, vector database or tool from the dashboard, the CLI, the API or a Deploy to Kilby button.
- Use Kilby from an AI agent: How an AI agent deploys and operates Kilby: the REST API and OpenAPI, the MCP server, which key to use, the safety model, and a worked example.
Build and run#
- Services: Web services, private services, workers and cron jobs: ports, health checks, start commands and instance types with list prices.
- Deploy from Git: Build a service from a Git repository instead of an image: public repositories by their address, private ones through GitHub, how new commits reach the service, and what happens when a host says slow down.
- Pull request previews: A preview of every pull request, at an address of its own, built on every new commit and removed when the pull request is closed or merged. What a preview copies from the service, and what it never does.
- Environment variables and secrets: Set variables and secret files for a service, generate random values, how they are stored, who can read them, and the limits.
- Environment groups: Define variables once and link them to many services: the precedence rule, what a change restarts, and how to manage groups in the dashboard, the CLI and the API.
- Projects and environments: Group the services, cron jobs and databases of a workspace into projects with environments such as Production and Staging. This organizes; it isolates nothing.
- Deploys, rollbacks and downtime: What starts a deploy, how a rolling deploy avoids downtime, why a service with a disk cannot, why a deploy fails, and how to roll back.
- Custom domains: Serve a web service on your own domain with a certificate Kilby issues and renews: DNS records, timing and every message.
- DNS AI: Host your domain's DNS on Kilby. Before the move, Kilby captures the records your domain answers today and checks each one in real DNS, so the site and the email keep working. Then point services at Kilby in one click.
- AI Gateway: Call AI models from your apps through one OpenAI-compatible endpoint, with a key per app, limits per key, a monthly cap and metered usage. Kilby's router picks the model for each prompt.
- Neuravision: Recognize your products on photos of retail shelves. Activate a plan, upload your product catalog, train it, publish a version, and send shelf photos to the API.
- Disks and scaling: Persistent disks, several instances and autoscaling on CPU, and how they count against the workspace limits.
- Logs, metrics and the shell: Read what a service prints, watch its CPU and memory, and open a shell in a running container.
- Log streams: Send the logs of your services to Datadog, an HTTPS endpoint, syslog over TLS, Grafana Loki or Better Stack. The page says whether it is available yet, and how it behaves when a destination is slow or down.
- Blueprints: Describe a stack of services and databases in one kilby.yaml, read the plan, then apply it.
Data#
- Databases: Managed Postgres with pgvector: create, connect, resize, back up and restore to any second of the last week.
- Key Value (Redis-compatible): A managed Redis-compatible store (Valkey) for queues, caches and rate limits. The page says whether it is available yet, and how it works when it is.
Teams and security#
- Workspaces, roles and 2FA: What a workspace is, the four roles and what each can do, adding members, two-factor authentication and sessions.
- Security and isolation: How workspaces are kept apart, how a service is confined, what is encrypted, and what Kilby does not claim.
- Kilby AI: What Kilby AI does with a failed deploy and in Kilby DNS, exactly what is sent to Google and what never is, its budget, and how to turn it on and off.
Automate#
- API keys and the API: Create an API key, pick its role, call the REST API, and find the full reference and the OpenAPI description.
- Webhooks and notifications: Get told when a deploy fails, a cron job fails or a shell is opened: by email, in a Slack channel, by signed webhooks, or call a deploy hook from CI.
- CLI: The kilby command line tool: logging in, listing services, reading logs, setting variables, and the exact help of each command.
Help#
- Limits and quotas: What a workspace may run, every other limit, and what Kilby says when you reach one.
- Troubleshooting: The failures Kilby recognises, the exact message each one gives, and what to change.
- Status page: Whether Kilby is up: the public status page and its JSON, what each component means, how a state is decided, and what the page cannot tell you.
Legal#
- Terms of Service: The agreement between you and Neuramorphic for using Kilby: accounts, your content, acceptable use, charges, suspension and termination, and liability.
- Privacy Policy: What personal data Kilby holds, why, who receives it, how long it is kept, where it is processed and how to exercise your rights.
- Subprocessors: The companies that process data for Kilby, what each does, what data it sees, where, and whether it is active today.
- Data Processing Addendum: How Neuramorphic handles personal data inside the content you run on Kilby: instructions, security, subprocessors, transfers, incidents, deletion and audits.
- Acceptable Use Policy: What you may not do with Kilby, how to report abuse, and what Neuramorphic does when a service or an account breaks these rules.
For AI agents#
Every page is plain Markdown too: add .md to its address, for example /docs/quickstart.md. /llms.txt is an index of the pages, /llms-full.txt is all of them in one file, and /api/v1/openapi.json describes the whole API. Ask for Accept: text/markdown and a page address answers with Markdown. Whether Kilby itself is up is at /status and /status.json.
Related#
- Quickstart: the shortest path to a running service.
- Use Kilby from an AI agent: how an agent should use Kilby.
- API keys and the API: authentication, roles and rate limits.