Hosting

Deckyard runs where you want it

The software is MIT licensed and made to be self-hosted, so running it yourself is the default path and always will be. But somebody has to keep that server patched, and not every organisation has that person. So we also run instances.

Two doors, same software

Not a free tier and a paid tier. The same code, either on your infrastructure or on ours, and the choice is about who does the maintenance.

Run it yourself

One line to try it, Compose to run it

One command puts Deckyard on your own machine at localhost:4177, picking Docker or Node 22+ automatically. Putting it in front of an organisation is the Compose path, with Postgres if you want it.

  • MIT licensed, with no feature held back for a paid edition
  • Your servers, your jurisdiction, your backup policy
  • Upgrade when it suits you, or never
Read the deployment docs

We run it for you

A dedicated instance, on your own domain

Your own Deckyard, not a tenant inside somebody else’s. Hosted in Europe, on your domain, with the upgrades, backups and certificates handled.

  • A separate instance, so your data is not pooled with anyone else’s
  • Your own hostname, with TLS set up and renewed
  • Upgrades, backups and monitoring handled
  • Export everything and walk at any time; it is the same software
Get in touch

On your own domain

It looks like your organisation, because it is

A managed instance sits on a hostname you choose and control, with the certificate issued in your name. There is no shared login page with somebody else’s logo on it, and no vendor domain in the URL your audience sees.

You point the DNS record; we do the rest.

What running it for you actually means

The honest list. No tiers, because there is nothing here we would hold back to sell you later.

  • A dedicated instance

    Your own database and your own application, not a row in a shared one. It can be moved to your own infrastructure later without an export-import dance.

  • European infrastructure

    Hosted in Europe under European law, which for a lot of public organisations is the part that decides whether this is usable at all.

  • Upgrades and backups

    New versions applied, backups taken and checked, certificates renewed. The work that makes self-hosting a commitment rather than an install.

  • A person who answers

    Small enough that support is a person who knows your setup, not a queue. That is also why we take on a limited number of instances.

Where the money goes

Hosting is what pays for the development

There is no venture capital behind Deckyard, and no plan to sell seats to as many people as possible. That means the money has to come from somewhere honest, and this is it.

Organisations that pay for a managed instance are funding software that everybody else can run for free. The roadmap follows the organisations actually using it, which is a very different pressure from following the organisations most likely to upgrade.

Tell us what you need

There is no signup flow, because this starts as a conversation rather than a checkout. Send an email and we will tell you honestly whether a managed instance or self-hosting fits you better.

Useful to mention

  • your organisation, and roughly how many people would make decks
  • whether you have a preferred hostname in mind
  • anything your procurement or privacy people will ask about