Museum hosting built for a collection, not a brochure.
A museum site is two things at once: a catalogue of thousands of objects with very large images, and a shop selling timed entry to a building with a fixed capacity. They fail in opposite directions.
Everything a catalogue asks of a host.
Very large source files, very deep archives and a ticket inventory that has to be exactly right. Each needs a different part of the stack configured.
Large originals processed in the background
A hundred-megapixel object photograph should not be resized while a curator waits for an upload to finish. Derivatives are generated as background work with limits sized for it.
Archives that stay queryable at scale
Collection records carry many taxonomies: period, medium, maker, gallery, acquisition. Those queries are indexed for how the archive is actually browsed rather than left to a generic meta lookup.
Timed entry that cannot be oversold
Capacity for a slot is decremented under a lock at the moment of purchase, so two people checking out simultaneously cannot both take the last place.
Object images delivered from the edge
Zoomable imagery is served as static files from the edge rather than rendered per request, so an exhibition going viral costs bandwidth instead of workers.
Rights-restricted material kept private
Not every image can be published. Restricted files live in paths that are not publicly listable and are served through signed links rather than obscure URLs.
Staging for a new exhibition
Build the exhibition, its objects and its ticket types on a clone, then push the whole thing at opening rather than editing it into existence in public.
The collection and the till in one view.
A museum site has a quiet failure and a loud one: a derivative queue that stopped, and a slot that sold twice. Both are visible here before a visitor finds them.
- One-click admin login, no shared passwords
- Per-site resource and storage view
- Plugin and core updates with per-item status
- Restore any daily backup from the dashboard
Eighteen thousand objects, filtered.
Browsing a collection is a taxonomy query with images attached. Whether it takes a moment or a second is decided by indexing and by where the images come from.
What we change for a museum site
These differ from a standard WordPress site on the same plan, and each follows from a catalogue whose source files are far larger than a normal site's.
| Setting | What we do | Why |
|---|---|---|
| Upload and memory limits | Raised for the admin and background contexts | Object photography arrives at sizes that exceed a normal upload limit, and a curator hitting that limit has no way to tell it apart from a broken site. |
| Derivative generation | Moved to background jobs rather than run during upload | Resizing a very large original inside the request that uploaded it is what makes bulk cataloguing time out halfway through an accession batch. |
| Archive queries | Indexes added for the taxonomy combinations the collection is browsed by | Collection records carry several taxonomies at once, and an unindexed combination scans the whole object set for every filter a visitor applies. |
| Ticket inventory | Slot capacity decremented under a lock | Timed entry sells a physical capacity, so two simultaneous checkouts reading the same remaining count is the difference between a full gallery and a queue of people holding invalid tickets. |
| Restricted media | Stored outside the publicly listable paths and served through signed links | Rights-restricted images are usually protected only by a difficult URL, which stops nobody once a single link is shared. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Our uploads fail on high-resolution object photography. Why?
How large a collection can WordPress handle?
Can timed-entry tickets be oversold?
How do we handle images we are not allowed to publish?
Can we prepare an exhibition privately?
Put the collection online without shrinking it.
Start in minutes, or let our team move your museum site across - no card, no commitment.