Intranet Hosting

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.

Every page authenticatedPermission-aware searchDocuments never public
Fully privatePermission-awareDocument controlDaily backupsFree SSL24/7 support
Built for staff only

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.

No anonymous view

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.

Filtered in 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.

Access

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
Public routes
Across the site
none
Search
Permission-filtered
enforced
Documents
Access-checked
private
Morning peak
Sign-in window
handled
Generation

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.

Object
cache doing the work
Filtered
search by permission
Planned
for the morning peak
MagicWP165 ms
Typical shared host1080 ms
Untuned VPS490 ms

Illustrative comparison of an authenticated intranet page. Your numbers depend on plugin load and permission complexity.

Configuration

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.

SettingWhat we doWhy
Page cacheOff across the site rather than bypassed per routeWith no anonymous visitors there is nothing to cache, and a rule that only bypasses some routes is a rule that will eventually miss one.
SearchPermissions applied inside the queryFiltering results after retrieval still exposes titles and excerpts of documents the searcher is not cleared for.
UploadsServed through access checks with no direct pathA forwarded document link that works outside the company is the most common intranet leak and the easiest to prevent.
Feeds and archivesClosed alongside pagesPrivacy plugins routinely secure the page template and leave the feed serving the same content to anyone.
Capacity planningSized for a concentrated morning peakStaff sign in within the same half hour, so an intranet's daily load is a spike rather than a curve.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Can the intranet be completely private?
Yes — no anonymous access to pages, search, feeds or uploads. That is more than most privacy plugins do on their own, which typically secure the page and leave the feed open.
Does search leak documents people cannot open?
Not when permissions are applied inside the query rather than to the results afterwards. Filtering after retrieval still shows titles and excerpts, which is often the sensitive part.
Can we use single sign-on?
SSO plugins work here. Tell us which provider you use and we will confirm before you commit rather than after.
Why is an intranet harder to make fast than a public site?
Because the usual first move is caching the front end, and there is no front end to cache. Speed has to come from the object cache and the database instead.

Keep the internal site internal.

Move the intranet across — migration is free, permissions included.