Hosting

Deckyard runs where you want it

Deckyard is MIT-licensed and made to be self-hosted. Your organisation can run it on its own infrastructure. If you would like to try it with colleagues and need someone to arrange the hosting, we offer a pilot: a managed instance for three months, in exchange for your feedback.

Two doors, same software

Both routes use the same software. The choice is about who runs the server and takes care of maintenance.

Run it yourself

Start with Docker Compose

The Compose setup includes the PostgreSQL database Deckyard requires. It builds the application from a repository checkout, using the supplied Caddyfile and your .env configuration. The Node 22+ route needs a PostgreSQL database of your own, database migrations and an application start step.

  • 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

Managed hosting

A dedicated instance, on your own domain

The pilot offer is a dedicated instance on your own domain. We intend to use European infrastructure; the provider, location and operational arrangements need to be agreed before a pilot starts. There are no managed customer instances running yet.

  • A separate instance, so your data is not pooled with anyone else’s
  • Your own hostname, with TLS set up and renewed
  • Agree on updates, backups and monitoring before starting
  • Moving the whole instance requires a database transfer and the upload directory
Discuss a pilot

On your own domain

Your domain, with your branding configured

You choose and control the hostname. Caddy obtains and renews a domain-validated TLS certificate for that hostname. The application starts with the Deckyard name; your application name, theme and brand assets need to be configured to make it your own.

The hostname needs a DNS record pointing to the server.

What to agree before the pilot

The pilot gives you a way to try Deckyard with colleagues. These are the hosting choices to work through together.

  • A dedicated instance

    The offer is a separate application and database. Moving an instance later takes a PostgreSQL dump and restore, plus the upload directory. The export in the app covers one user’s presentations.

  • European infrastructure

    European hosting is the intention. Choose the provider and location, and review the processing agreements your organisation needs, before starting.

  • Upgrades and backups

    Decide who applies updates, makes backups and tests restores, and how monitoring is arranged. Certificate renewal is automated by Caddy; the application does not schedule backups.

  • Contact and expectations

    Discuss what help your organisation needs and what can be arranged for the pilot. Support and availability need their own agreement.

Where the money goes

Hosting as a way to fund development

There is no venture capital behind Deckyard. The intention is to fund development through managed hosting while keeping the software freely available to run yourself.

There is no hosting revenue yet. Pilots are a way to learn what organisations need in practice; that feedback can help decide what to build next.

Discuss a pilot or hosting

The pilot offer is a managed instance for three months, in exchange for your feedback. Email Jaap about what you would like to try with your organisation and how you want to arrange hosting.

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