Intranet hosting where nothing is public.
An intranet has no anonymous visitors at all. That removes the technique every other WordPress site leans on, and changes what the hosting has to be good at.
No public pages, no page cache.
The usual first move. Cache the front end - does not exist here, so the work goes everywhere else.
Authenticated from the first request
There is no anonymous view of anything, including search results and uploaded files. Access is checked before content is assembled rather than hidden in the template.
Search that respects permissions
Internal search has to exclude what the person searching is not allowed to see. Filtering results after retrieval leaks titles, so permissions are part of the query.
Speed from the object cache
With no page cache to lean on, the object cache and a tuned database are what make an intranet feel quick - every page is generated for the person asking.
Documents that are not URLs
Policies, contracts and handbooks are served through access checks, so a link forwarded outside the company does not work for whoever receives it.
Everyone is logged in at nine
Intranet traffic arrives in a narrow band each morning rather than spread across a day, and capacity is planned for that shape.
Private means private, including search.
Most WordPress privacy plugins hide content in the template while leaving it in search results, feeds and uploads. On an intranet each of those is a leak.
- No anonymous access to any route
- Search results filtered by permission
- Uploads served through access checks
- Feeds and archives closed as well as pages
Every page built for one person.
With page caching off the table, an intranet's speed comes entirely from how fast it can assemble a page that only one person will ever see.
What we change for intranets
One property drives all of it: there is no anonymous traffic, so there is nothing a page cache can hold and nothing that may leak.
| Setting | What we do | Why |
|---|---|---|
| Page cache | Off across the site rather than bypassed per route | With no anonymous visitors there is nothing to cache, and a rule that only bypasses some routes is a rule that will eventually miss one. |
| Search | Permissions applied inside the query | Filtering results after retrieval still exposes titles and excerpts of documents the searcher is not cleared for. |
| Uploads | Served through access checks with no direct path | A forwarded document link that works outside the company is the most common intranet leak and the easiest to prevent. |
| Feeds and archives | Closed alongside pages | Privacy plugins routinely secure the page template and leave the feed serving the same content to anyone. |
| Capacity planning | Sized for a concentrated morning peak | Staff sign in within the same half hour, so an intranet's daily load is a spike rather than a curve. |
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 the intranet be completely private?
Does search leak documents people cannot open?
Can we use single sign-on?
Why is an intranet harder to make fast than a public site?
Keep the internal site internal.
Move the intranet across. Migration is free, permissions included.