We run it. You still own it.
Hosted MyCRM is your own dedicated instance — your own process, your own database, your own encryption key — running the identical binary you could run on your own server. We handle the box, the updates, the backups and the recovery. What we never do is turn ownership into a subscription you cannot leave: your instance is a data directory, and that directory is yours.
What “hosted” actually means here
Not a shared database with your rows in it. A separate instance per customer — the same isolation you would get running it yourself, minus the operations.
Your own instance
- One process and one database that are yours alone — not a tenant column in a shared table
- Your own master key, sealing your own connector credentials
- Your own subdomain:
you.iowncrm.net, on a certificate we obtain and renew - The whole feature set. There is no hosted-only tier and no self-host-only tier
The same artifact
- The binary we run for you is byte-for-byte the one on the self-hosting page
- The same REST API at
/api/v1, the same scoped keys, the same embedded UI - Nothing is held back to make leaving harder — because leaving is the test of whether you own it
- SQLite under the hood, so your entire instance is a directory that copies in seconds
The operations, so you do not have to page yourself.
This is the actual list of what “managed” buys you. Every item is something a self-hoster would otherwise own.
Provisioning
A purchase stands your instance up on our fleet — a container of its own, packed onto a shared box with other single-instance tenants but sharing nothing with them. Its DNS record, its certificate and its sign-in link are ready without a ticket.
Updates
We roll new versions out and restart the instance. Schema changes apply on boot; your records, deals, notes and API keys survive a version change untouched. You are never the person who forgot to patch on a Tuesday.
Encrypted backups
Your instance snapshots itself on a schedule and uploads the copy to us sealed with a key derived from your account. We hold ciphertext, not the key — the store is zero-knowledge, so a backup is useless to anyone who cannot already open your account. The snapshot is consistent while the instance keeps serving.
Moves & disaster recovery
If a machine has to change, your instance moves to another one as a freeze, a copy and a restart — your hostname never changes and no record is lost, because the master key travels inside the encrypted snapshot. If a box is ever lost outright, we restore your instance from a stored backup only your account’s key can open.
What happens the day you want to leave?
Every hosted product has an answer to this. Most of them are an export button that gives you a CSV and keeps the working system. Ours is different, and it is the whole reason to trust the hosted option.
You get the running system, not a dump
We hand you the data directory — the SQLite database and the master key, together. It is the same binary, so it boots on your own box with the same contacts, the same timeline, the same deals, the same sealed connector credentials and the same API keys. Nothing to re-key, nothing to re-import.
Hosted and self-host are one road, both directions
Start hosted and move to your own server later, or start self-hosted and hand us the directory when operations stop being fun — it is a copy either way, because it is one artifact. That is the only version of “no lock-in” we think is worth printing.
What hosting includes — and what it deliberately does not.
Included
- A dedicated instance, provisioned, on your own subdomain with TLS
- Updates, applied by us
- Daily encrypted, zero-knowledge backups — and the restore, when it is needed
- Machine moves with a stable hostname and no data loss
- Monitoring of the instance’s health and readiness
- Every product feature — connectors, forms, import/export, the full API, playbooks
Not included
- Any feature the self-host build does not have. Hosting is operations, not a bigger product
- Us reading your data. The backup store is zero-knowledge, so we cannot browse your records to debug for you — you would export or share what you want us to see
- A per-seat charge dressed up as hosting. Adding your sixth user does not add a line item
- Lock-in. The exit is a file copy, by design
Pricing is still being finalised.
Rather than print a figure we might change next month, the pricing page reads the live registry and says “contact us” for hosted until the rate is settled. Tell us your team size and we will quote you in writing — and set up a trial instance so you are deciding on the real thing, not a screenshot.
Let us stand one up for you.
Tell us which systems your customer data lives in today. We will provision a trial instance, wire the connectors, and you will be looking at your own customers on your own subdomain — not a demo dataset.