A control panel for servers you run yourself
What SrvYard is and why it exists, the principles it is built on, what it does not support, how it is built and who operates it.
- Product
- A control panel for servers you run yourself
- Operated by
- Spykra Technologies UK Ltd
- Registered
- England & Wales, No. 14554019
- Runs on
- Ubuntu 24.04 LTS and 26.04 LTS
- Servers
- Yours, in your own cloud account
- Contact
- [email protected]
SrvYard is a control panel for servers you run yourself. You give it a machine, either one it creates at a cloud provider or any Ubuntu server you can reach over SSH, and it installs the software and then manages sites, deployments, certificates, databases, backups, monitoring and teams from one dashboard.
Why it exists
Running your own servers should not mean doing every step by hand over SSH, and it should not mean handing the machines to a platform. SrvYard does the repetitive work (installing software, deploying releases, renewing certificates, taking backups) and shows you the output, while the servers stay in your own cloud account. The list of principles and the list of things it does not do are further down this page, so you can rule it out quickly.
How it works
SrvYard has a web app, an SSH engine and background jobs. For every change, the engine logs in to your server with a key it generated for that server and runs a prepared script. After the first setup it connects as its own srvyard user, not as root. Long operations run as jobs, so the page shows a state such as Installing and updates by itself.
Nothing runs inside SrvYard. Your sites run on your machines, in your provider account, and you pay the provider directly. If you stop using SrvYard, the servers, sites and databases keep running exactly as they were. Read What SrvYard is and how it works for the longer version.
What it supports
- Sites: Laravel, Symfony, Statamic, WordPress, phpMyAdmin, plain PHP, Next.js, Nuxt, static HTML, and an "Other" type with your own deploy script.
- Runtimes: PHP 8.1 to 8.5 side by side, and Node.js 22, 24 and 26.
- Servers: Ubuntu 24.04 LTS and 26.04 LTS, created at Hetzner, DigitalOcean, Vultr, Akamai (Linode), Amazon EC2 and Lightsail or Proxmox VE, or any Ubuntu server you bring.
- Databases: MySQL, MariaDB and PostgreSQL, plus Redis, Memcached and Meilisearch.
- Automation: a REST API and webhooks.
Moving in and out
You can move in from Ploi or VitoDeploy with a read-only import, and from any other Ubuntu server by scanning and adopting it. Leaving is as plain: cancelling a subscription does not touch your servers, and an organisation's configuration can be exported (without secrets, or with them sealed under a passphrase you choose).
Getting help
The documentation is searchable and has a chat that answers from it. Tickets need an account, so we know whose servers we are talking about. For a question before you sign up, or a security report, use the contact form.
Principles
What the product does about each one
Your servers, your cloud account
SrvYard creates machines in your account or connects to ones you already have. It never hosts your sites, and you pay your provider directly with no mark-up.
Boring and reversible
It runs the commands you would run by hand and shows you the output. Cancel and the servers keep running as they were; a configuration can be exported.
Honest limits
The list of what it does not do is on this page and in the FAQ, not in a footnote. A rollback does not undo migrations, and the health check does not roll back by itself.
Read-only imports
Moving from Forge, Ploi or VitoDeploy uses a read-only token. Nothing is changed in the old panel, and nothing on a live server changes until you have read the plan.
One-time credentials
Tokens, webhook secrets, and the sudo and database passwords it generates are shown or downloaded once. A lost one is regenerated, not read back. How secrets are handled.
What we do not support
Said up front
| Docker, Docker Compose, Kubernetes | Not deployed or managed. Sites run on Nginx and PHP-FPM or Node on the host. |
|---|---|
| Python, Ruby, Go, Java, .NET | Not managed site types. The Other site type runs your own deploy script, but installing that runtime is your work. |
| Other operating systems | Ubuntu 24.04 LTS and 26.04 LTS only. No Windows servers, no other Linux distributions. |
| Hosting | SrvYard does not host your sites, register domains or host email. |
| Command line | There is no command line tool. Use the dashboard or the REST API. |
How it is built
The stack your own Laravel apps use too
| Application | Laravel 13 on PHP, the same framework SrvYard deploys for its customers. |
|---|---|
| Console | Inertia 3, React 19 and TypeScript, styled with Tailwind CSS 4. |
| Background work | Queued jobs on Redis, watched by Horizon. A long operation is a job, so the page shows a state such as Installing and updates by itself. |
| Server access | An SSH engine that runs prepared scripts on your server with a key generated for it, as the srvyard user after the first setup. |
| API | REST, described by an OpenAPI 3.1 file with 376 operations. Webhooks are signed with HMAC-SHA256. |
| Sign-in | Laravel Fortify with two-factor, passkeys and optional GitHub, Google, GitLab and Apple sign-in. |
| Billing | Stripe, through Laravel Cashier. |
| This website | Laravel 13 and Blade, server-rendered, with its copy kept in the SrvYard admin. |
The operator
Who is behind it
SrvYard is operated by Spykra Technologies UK Ltd, a company registered in England & Wales (No. 14554019). The legal documents name the operator and say how your data is handled.
Platform data is stored in the UK and EU. UK / EUPlatform data stays in the UK and EU
- Company
- Spykra Technologies UK Ltd
- Number
- 14554019
- Address
- 86–90 Paul Street, London, England, EC2A 4NE, United Kingdom
- [email protected]
- Phone
- +44 (0)7769 243907
Connect a server. Deploy a site. Read the log.
Free: 1 server, 3 sites, 100 deploys a month. Read the docs first if you prefer.