Skip to content
The hosted control plane for your own servers

Deploy to your own server,without touching a terminal

RunsNext.js

Connect a VPS with one command and get a portal that builds and runs your Dockerised applications behind automatic HTTPS — with monitoring, request analytics, and alerts built in. Push to your branch and it ships itself.

Get startedExplore features
What happens after a push: Webhook signature verified, Repository cloned, Image built, Health check passed, Live on https://your-app.example.com.
command to connect a server
1
inbound ports to open
0
between monitoring samples
15s
AI crawlers and agents recognised
35

How it works

From a bare VPS to a live app in three steps

  1. 01

    Connect your server

    Run the command the portal gives you on any VPS. A small agent dials out to us — no port to open and no SSH key to hand over.

  2. 02

    Point it at your code

    Choose a repository and branch, or upload a ZIP. A Compose file, a Dockerfile, or Nixpacks builds it — whichever your project has.

  3. 03

    Push, and it ships

    Every push is built, health-gated, and served behind HTTPS. If something is wrong, roll back to the previous image in one click.

Everything in one portal

The whole platform, on a server you already pay for

Deployments, domains, databases, monitoring, analytics, and alerts — each one built to run on a small VPS without a second bill.

  • Your own servers

    One command connects a VPS you already own. Nothing inbound is opened.

  • Git deployments

    Push to your branch and it ships itself — built, health-gated, and rollback-ready.

  • Domains and HTTPS

    Add a hostname, create the record it shows you, and HTTPS arrives on its own.

  • Environment variables

    Encrypted, write-only configuration that never touches the disk.

  • Managed databases

    One-click PostgreSQL, Redis, and MinIO with scheduled backups.

  • Server monitoring

    CPU, memory, disk, network, and every container — including steal time.

  • Request analytics

    Every request to every app — read from the proxy, with no script to install.

  • AI traffic

    See which AI crawlers read your site, verify them, and catch the impostors.

  • Alerts

    Alerts that open and resolve themselves — in the portal, email, webhook, or Telegram.

  • Teams and security

    Organizations, roles, passkeys, two-factor, API tokens, and an audit log.

AI traffic

Know which AI reads your site

Every request is sorted into a traffic class. See which crawlers came, which operator runs them, and which pages they read — each claim checked against the address ranges its operator publishes, so impostors stand out.

See AI traffic

Recognised today

Model training

  • GPTBot
  • ClaudeBot
  • CCBot
  • Bytespider
  • meta-externalagent
  • Amazonbot
  • MistralAI-Training
  • cohere-ai
  • Diffbot

AI search

  • OAI-SearchBot
  • Claude-SearchBot
  • PerplexityBot
  • Google-CloudVertexBot
  • meta-webindexer
  • Amzn-SearchBot
  • MistralAI-Index

Asked by a person

  • ChatGPT-User
  • Claude-User
  • Perplexity-User
  • Gemini Notebook
  • NotebookLM
  • DuckAssistBot
  • meta-externalfetcher
  • Amzn-User
  • MistralAI-User

Acting for a user

  • ChatGPT agent
  • Google-Agent

Search engines

  • Googlebot
  • Bingbot
  • Applebot
  • DuckDuckBot
  • YandexBot

Visitors sent by

  • ChatGPT
  • Perplexity
  • Claude
  • Gemini
  • Copilot
  • DeepSeek
  • Grok
  • Meta AI
  • Le Chat
Your VPS opens one outbound websocket to the Sthora control plane; no inbound port is opened on the server.

Your server, our control plane

We run the portal. You keep the machine.

The control plane manages servers you already own. One outbound connection carries every command, so your firewall stays shut and your data stays where it is.

  • Your machine, your data, your Docker daemon. We hold no credential to it beyond a token you can rotate.
  • Your applications are containers on your machine. They keep running if the connection drops.
  • Stop the agent and the connection is gone — nothing is left listening.
How connecting works

Security

Admin on the portal is root on your server. We built it that way.

The platform drives the Docker daemon on your machine, so that access has to be narrowed by the platform rather than trusted. Everything below follows from it, and each guard has a regression suite whose purpose is to stay unbroken.

  • Compose files are judged

    Privileged containers, host namespaces, and stray bind mounts are refused before Docker sees the file.

  • Hostnames cannot be claimed

    Every routing label in your file is replaced with the platform’s own.

  • Uploads cannot escape

    An archive with one entry outside its destination is refused whole.

  • Secrets stay write-only

    Encrypted at rest, scrubbed from logs, and returned by no endpoint.

Teams and security

FAQ

Questions, answered

Do you need access to my server?

It needs an agent running on it. The agent dials out to the control plane over one outbound connection, so you open no port and write no firewall rule. It authenticates with a token you can rotate or revoke from the portal at any time.

What can I deploy?

Anything that runs in a container: a Docker Compose file, a Dockerfile, or — for a repository with neither — a Nixpacks build. NestJS and Express backends, React, Next.js, and TanStack Start frontends, and full-stack applications all fit.

Which Git hosts work?

Any of them. A generated deploy key works with GitHub, GitLab, Bitbucket, and self-hosted hosts, and push webhooks are accepted from each. The optional GitHub App adds a repository picker and reports deployment status back onto the commit.

Is there downtime when I deploy?

By default the old containers stop and the new ones start, which is a few seconds. Blue/green is an opt-in per application, gated on a free-memory check so a small server is never pushed over by running two versions at once.

Do I need to add a script for analytics?

No. Request analytics are read from the reverse proxy on your server, so every request is counted — including from clients that never run JavaScript — without a tag or a cookie.

What happens to my applications if I stop paying?

They keep running. They are containers on your machine, started by Docker Compose files the platform wrote to your disk — nothing about them depends on the control plane staying reachable. You lose the portal, not the workloads.

What is not included?

Kubernetes, Swarm, multi-node scheduling, autoscaling, per-pull-request preview environments, a bundled Prometheus or Grafana, serverless functions, and a CDN. Each is a rabbit hole a small VPS cannot afford, and pretending otherwise would make the rest worse.

Your server is ready when you are

Create an account, connect a VPS, and ship your first application.

Get startedSee pricing