Manufacturing hosting for catalogues that sell on specification.
A manufacturer's site has no basket. It has datasheets, part numbers and engineers filtering on tolerances, and each of those is a different hosting question.
Everything a manufacturer's catalogue asks of a host.
Products described in numbers, documented in PDFs, and kept in the range for a decade. None of that behaves like an online shop.
Datasheets delivered from the edge
Specification PDFs and CAD files are served through the edge cache with byte-range support, so a fifty-megabyte drawing downloads without occupying a PHP worker for the duration.
Filters on real attributes
Voltage, tolerance, material and dimension filters run against indexed columns, so an engineer narrowing a range of four thousand parts gets an answer rather than a timeout.
Part numbers that survive a redesign
Product URLs are treated as permanent and redirects are carried through rebuilds, because a part number gets cited in drawings and purchase orders long after a website changes.
A distributor area that stays private
Trade pricing, stock levels and ordering documents sit behind authentication and outside the cache, kept separate from the public catalogue everybody else sees.
Catalogue pages that cache completely
Without a basket there is nothing per-visitor on a product page, so the public catalogue is entirely cacheable - which is the advantage most manufacturer sites never take.
One catalogue, two audiences.
The public catalogue and the distributor portal are the same site with entirely different requirements, and the failures come from treating them as one thing.
- Document download and bandwidth view
- Distributor access and login audit
- One-click admin login for the marketing team
- Restore any daily backup from the dashboard
Filtering four thousand parts on three attributes.
An engineer with a specification in hand filters before they read anything at all. That query is the site's real front door.
What we change for a manufacturer's site
These are the settings that differ from a standard WordPress site on the same plan. Each follows from a catalogue that is technical, document-heavy and long-lived.
| Setting | What we do | Why |
|---|---|---|
| Document delivery | Datasheets and drawings served from the edge with byte-range support | A large PDF sent through PHP holds a worker for the whole download, and engineers routinely pull several at once. |
| Attribute filters | Indexed columns for technical specifications | Filtering on a tolerance or a voltage stored as postmeta reads every product row for every single filter click. |
| Product URLs | Permanent, with redirects carried through redesigns | Part numbers appear in drawings and purchase orders that nobody is going to reprint because a website was rebuilt. |
| Distributor portal | Authenticated and excluded from cache, separate from the public catalogue | Trade pricing served from a cache shared with the public site is trade pricing that is no longer confidential. |
| Public catalogue cache | Long lifetimes, since nothing on a product page is per-visitor | There is no basket to invalidate, so anything short of an aggressive cache leaves the easiest available performance win unused. |
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.
Can engineers filter on technical specifications?
How do you serve large CAD and PDF files?
Will our part number URLs keep working?
Can we have a private area for distributors?
Do we need WooCommerce if we do not sell online?
Move your catalogue to a host that understands specifications.
Free migration, datasheets from the edge, and part numbers that keep resolving.