What 'Single-Tenant' Actually Means for Your Gallery Data

When you sign up for most SaaS software, your data goes into a shared database alongside data from every other customer. This is the multi-tenant model. It is economically efficient for the vendor — one database, one set of servers, one set of backups. But it means your gallery’s collector list, inventory, pricing, and private sale history is stored in the same place as every other gallery’s data.

Galexivo does not work this way.

Your data, your Cloudflare account

When you sign up for Galexivo, we deploy a fresh copy of the entire platform to your own Cloudflare account. Your database (Cloudflare D1), your file storage (Cloudflare R2), your Workers (the application layer) — all of them belong to you and run under your Cloudflare account credentials.

We never have a copy of your data. We cannot query your collector list. We cannot look at your inventory. We cannot accidentally expose your data in a breach of our systems, because your data is not in our systems. It is in yours.

Why this matters

Portability. If you decide to stop using Galexivo, you own your data in a portable format. Your D1 database can be exported. Your files in R2 are standard object storage. You are not locked in.

Security isolation. A security vulnerability in another customer’s account cannot affect yours. In a multi-tenant system, a single misconfigured permission or a SQL injection in one tenant’s code path can sometimes read another tenant’s data. In Galexivo’s architecture, this is structurally impossible — your data is not in the same database.

Compliance. Some collectors and artists, particularly in jurisdictions with strict privacy laws, have concerns about where their data is stored. When all data is in your Cloudflare account, you can tell them: your information is stored in a Cloudflare data centre in [your chosen region]. That answer is often sufficient for even careful buyers.

Price stability. Your costs are your Cloudflare bill plus Galexivo’s subscription. Cloudflare’s free tier covers the majority of gallery workloads indefinitely. Even if you scale beyond the free tier, you control the infrastructure and can optimise it. We have no incentive to increase your costs by storing more of your data than necessary, because your data is not costing us anything.

What this means for the setup

The trade-off for single-tenant architecture is setup time. Instead of creating an account and logging in immediately, you connect your Cloudflare account, and we provision your instance. This typically takes about ten minutes.

We walk you through the process step by step in the onboarding wizard. If you already have a Cloudflare account, the connection is a two-minute authorisation flow. If you do not, creating one is free.

Once provisioned, your instance runs independently. Updates to the Galexivo platform are delivered as code deployments — you will always be on the latest version without any data migration required.

The vendor lock-in question

The most common question we get about the single-tenant model: “If I leave Galexivo, what happens?”

The direct answer: your Cloudflare resources continue to run. Your Workers keep serving your public gallery. Your database stays intact. Your files stay in your R2 bucket. Nothing we do — including going out of business — can take your data away from you.

The Galexivo application itself is deployed to your Workers. If you wanted to fork it or replace it, you could. The code is not open-source today, but the architecture ensures you are never dependent on our continued operation for your data to remain accessible.

We think this is the right way to build software. Not everyone agrees. If you prefer the convenience of a traditional SaaS setup where you do not think about infrastructure, Galexivo may not be for you. But if you have built a business around relationships and assets that you genuinely own, Galexivo is built on the same philosophy.