xhostd
Sign in Start building
Product

Hosting your AI coding agent can drive.

Hosting, a Postgres database, sign-in, and safe places to test.
Ready the moment your agent asks for them.

How an app goes live

Four steps, and your agent does the first three.

  1. 1

    Your agent pushes the code

    It commits files through the API, or pushes to the app's git repository.

  2. 2

    xhostd builds it

    The platform builds an image from your scripts or your Dockerfile.

  3. 3

    A channel runs it

    One always-on container with its own HTTPS address, database, and files.

  4. 4

    You go live, or go back

    Deploy the same revision to production. If something breaks, roll back.

Break things in staging. Production never notices.

You can create multiple apps. Every app starts with a prod channel. Add more channels, such as staging for testing or one per new feature, and give each the name you choose.

prodProductiontrail-notes-alex.xhostd.app
stagingStagingstaging-trail-notes-alex.xhostd.app
photo-uploadFeature previewphoto-upload-trail-notes-alex.xhostd.app

Every channel has its own

  • HTTPS address and custom domains
  • Postgres database, for apps that run code
  • File storage
  • Settings and secrets that override the app's defaults
  • Always-on container, with no cold starts

Each channel keeps its own data and files, so a test never touches production data. The whole app can share settings and secrets, and a channel can override them. One account can hold many apps. Each app counts one channel for production, and channels come from your plan's allowance. How channels work.

Pick how your app runs

Start from a template, or bring your own Dockerfile.

KindWhat you deployGood forExample
Static siteHTML, CSS, and JavaScript, served by nginx. No process and no database.Landing pages and portfoliosStatic site recipe →
Python appA Python 3.13 FastAPI service, started by your launch script.APIs and web appsPython recipe →
Node.js appA Node 22 Express service, started the same way.APIs and web appsNode.js recipe →
Background workerA loop that serves no HTTP and stays on.Queues and long jobsWorker recipe →
Docker appYour own Dockerfile, within your plan's image size.Any language or packageDocker recipe →
Raw TCP serviceAny protocol on a public port. Paid plans only.Game servers and brokersTCP recipe →

Where everything lives

Every part of an app has a home, and a way out.

WhatWhere it livesHow it is kept
CodeThe app's git repositoryClone it any time.
DatabasePostgres, one per channel. Static sites have none.A snapshot every night, and one before every deploy.
FilesS3-compatible storage for each channelIncluded in the nightly snapshot.
Settings and secretsEnvironment variables: an app default, with overrides for each channelEncrypted at rest. Your agent can set a secret but cannot read it back unless you allow it.

The free plan keeps nightly snapshots for 24 hours and the last deploy snapshot. Paid plans keep them for 7 days and the last 3. To leave, clone the repository, or export a project with its database dump and a Docker Compose setup. Data and recovery guide.

Stay in control of a running app

Do it all in your console. Your agent can read most of it too.

Manage it

Change anything after launch.

  • Deploy a revision, or roll back
  • Set variables and secrets for each channel
  • Add domains and create test channels
  • Create and revoke access keys

Watch it run

Health and usage, any time you look.

  • Health findings, with what to do about them
  • Usage against your plan
  • Build and runtime logs
  • An activity feed of what happened

Know your visitors

Traffic analytics, with no script in your pages.

  • Visits, unique visitors, and top pages
  • Broken links, and status codes
  • Time of day and visitor countries

Keep the decisions

Some actions always need you.

  • Revealing secrets, and opening a public TCP port
  • Upgrading your plan, in the console
  • Transferring a project, only in the console

Compared with running it yourself

Work you would otherwise plan, build, and maintain. Read the full comparison.

TaskOn your own serverOn xhostd
HTTPSGet certificates and renew themIssued and renewed for you
DatabaseInstall Postgres, tune it, and set up backupsOne per channel, with nightly snapshots
DeploysWrite and maintain a pipelineYour agent pushes and deploys
Test environmentsBuild and pay for a second stackAdd a channel from your allowance
Custom domainsSet up DNS and TLSAdd two DNS records and verify
MonitoringSet up tools for health and logsHealth, usage, and logs on demand

Works with the agent you already use.

Connect over MCP, or drive xhostd through the HTTP API and git. See all the tools your agent gets.

All setup guides →

Priced by resources, not people.

Start free, then pick the capacity you need. Your price follows the resources you use.

See Pricing →