Run Deliverd your way: hosted, dedicated, self-hosted or as a partner

Deliverd sits at a sensitive point in your AI work. It is where an agent stops and asks a person, where the answer is recorded, and where an auditor later reads what happened. So it matters where it runs, and who runs it.

For most teams the answer is simple: use it on deliverd.dev, stored and served from London, and let us keep it running. For some it isn't. A bank wants its own copy. A public body has a network that never touches the internet. A consultancy wants to run it for twenty clients without twenty subscriptions. So Deliverd now comes four ways.

Hosted on deliverd.dev

This is where everyone starts, and where most stay. Sign up, connect an agent, and its first request reaches a person in minutes. Free has no time limit, and the paid plans on the pricing page add Objectives, Compliance Mode and governance across the organisation. We run it, update it and back it up.

Choose it if you want to start today and have no rule that says your records must sit on infrastructure you control.

Dedicated

A copy of Deliverd for your organisation alone, run and updated by us, in the region you choose. Nobody else's data shares its database. You get the same product and the same releases, without sharing anything with anyone else.

Choose it if your security or procurement team asks for single-tenant hosting, or a region we don't otherwise serve.

Self-hosted

Run Deliverd on your own infrastructure from our container image. One image runs the app, the scheduled jobs and the database upgrades, and a single compose file brings up everything it needs on one machine. Your approvals, reviews and evidence never leave it.

It also works on networks with no outside connection at all. The licence is checked on the machine itself, so nothing needs to call home for the product to work.

Choose it if your policies, your regulator or your own risk appetite say the record of who approved what has to live inside your walls.

Partner edition

For consultancies, integrators and managed service providers who build and run AI for other organisations. Run Deliverd for your clients on your own infrastructure and domain, with each client's name and logo on what their people read. Each client keeps its own policies, approvers and audit log, and your people can work across all of them with one sign-in.

White-label terms are agreed with each partner. The partner programme explains how to apply.

Choose it if Deliverd is part of what you deliver to clients, and you want it to sit in your stack rather than beside it.

What a copy tells us, and what it doesn't

A dedicated or self-hosted copy runs on a signed licence. Once a day it sends us counts only: how many organisations, how many seats, how many decisions this month, and which release it is on. No names, no content, no records. That is how we know which copies need an update and how usage is billed. An air-gapped copy sends nothing; its administrator downloads a signed usage file once a month instead.

If a licence ends, there are thirty days of grace. After that the copy stops taking new approval requests and says why. Everything already recorded stays readable, decidable and exportable. Nothing is deleted or hidden because of a licence.

How to choose

• Just want to start? Use deliverd.dev, and move later if you need to.
• Need single-tenant, but don't want to run servers? Dedicated.
• Need it inside your own walls, or offline? Self-hosted.
• Delivering AI to clients? Partner edition.

There is no price list for the last three. Each is quoted for the way you'll use it, so the pricing page sends you to the team. Tell us what you need and we'll come back with a plan.