What Is an Intranet? Definition, Uses, and Modern Examples

TL;DR. An intranet is a private network inside an organisation that lets employees share information, collaborate, and access internal systems behind controlled access. The word covers a wide range of shapes — from a single SharePoint site to a federated set of focused tools (a wiki, a chat app, a file store). In 2026, most working teams have replaced the monolithic intranet with a small stack of focused tools that each do their job well. The term survives; the shape has changed.

Shadow, our security lead, has opinions about intranets. Most of them are [REDACTED]. The opinions that aren’t classified boil down to the intranet is the access boundary, the wiki is the surface most people use, and the part of the intranet that loads in eight seconds is the part that no one uses. What is intranet as a working concept in 2026, then? It’s a controlled-access network with a few content surfaces on top of it. The interesting questions are about which surfaces, how fast they should be, and whether your team needs a single portal or a small federation of focused tools. Sub-second loads. Keyboard-first. Shadow will not comment.

What an intranet actually is

An intranet is a private computer network used inside an organisation. The defining property is the boundary: the people inside can reach the resources, the people outside cannot. The shape of the resources varies — pages, files, directories, forms, dashboards, chat — but the boundary is the constant.

The Wikipedia entry for intranet gives the canonical definition: a computer network for sharing information, easier communication, collaboration tools, operational systems, and other computing services within an organization, usually to the exclusion of access by outsiders. The “usually to the exclusion of” is doing the load-bearing work. An intranet is defined by who can’t get in as much as by what’s on it.

In 2026, the word means at least three different things depending on who’s saying it:

Old-school technical: the LAN, the IP block, the internal-only DNS, the VPN, the firewall — the infrastructure layer.
Mid-2000s product: the SharePoint or Confluence-style portal — a single web app that hosts the company’s pages, files, and announcements.
Modern operating-discipline: a federated stack of focused tools (a wiki, a chat app, a file store, an identity provider, an HR system) sitting behind shared single sign-on.

All three definitions are valid. The mid-2000s one is the most-quoted; the modern one is what most working teams actually run.

Intranet vs internet vs extranet

The three terms get conflated; the distinction is straightforward.

Network	Who’s on it	What it’s for	Access boundary
Internet	The whole world	Public information, commerce, communication	Open — anybody with a connection
Intranet	Employees of one organisation	Internal docs, tools, communication, operations	Closed — needs authentication / VPN / SSO
Extranet	Employees + selected outsiders (customers, suppliers, partners)	Cross-organisation collaboration on a controlled scope	Half-open — auth required, but invites cross the boundary

The mnemonic that survives: intra means within, extra means outside, inter means between. An intranet is within one organisation. An extranet extends to controlled outsiders. The internet connects everything.

A practical consequence: the question “is this an intranet or an extranet?” often comes down to “is the customer portal behind the same auth wall as the employee tools?” If yes, it’s an intranet shared with customers — uncommon and risky. If no — the more common pattern — the customer-facing surface is an extranet, and the employee-facing surface is the intranet proper.

How an intranet actually works

The underlying technology is the same as the public internet — TCP/IP, HTTP, DNS. The differences sit one layer up:

Auth at the boundary. Single sign-on (SSO) is the modern default. An employee signs in once; the SSO provider issues a token that every internal tool trusts. The auth provider is the intranet’s front door.
Network-level isolation, where it’s needed. Some resources live on a private network reachable only from the office network or via a VPN. Most modern intranets keep most surfaces on the public web behind SSO — VPN gates only the sensitive subset (database admin, internal-only dashboards, build servers).
DNS that resolves internal-only. Internal services often have hostnames that resolve only inside the corporate network — wiki.corp.example.com works from the office; outside it does not.
Content surfaces on top. The wiki, the chat app, the HR system, the issue tracker — these are the things people actually click on. They sit on top of the auth + network layer.

The five-thousand-word version of how do intranets work is a sales pitch for a specific platform. The four-bullet version above is most of what a working developer needs to know on a Tuesday afternoon.

What people use intranets for

The use cases have not changed much in two decades. The tools that satisfy them have changed a great deal.

Use case	What the monolithic intranet did	What the modern federated stack does
Onboarding	A page in SharePoint, often last edited 2019	A wiki page with current ownership and an edit timestamp visible
Company announcements	An intranet homepage	A Slack channel and an archive surface
HR docs (policies, benefits, payroll)	A SharePoint folder	A dedicated HR system + a wiki space
Operational docs (runbooks, ADRs, postmortems)	A wiki module bolted onto the portal	A dedicated wiki — the durable half of the intranet
Internal directory (who-is-who)	An intranet feature, often broken	An identity provider’s directory, surfaced in chat
File sharing	A network drive	A cloud storage provider
Internal forms	Custom-built intranet apps	A workflow tool plus an SSO-gated dashboard

The trend across two decades is the same: tools that started as features of one big portal became standalone products that do their one job well. The intranet didn’t vanish — it unbundled.

Why corporate intranets feel slow

Honesty section about the failure mode. The complaint about corporate intranets is universal: they feel slow, and the search bar lies. This is not nostalgia. Most monolithic intranets from the 2010s — SharePoint deployments, custom Confluence portals, Jive sites, Workplace by Facebook (RIP) — routinely answered a page click in 2-4 seconds, sometimes longer when the homepage had ten widgets each making three upstream requests. A team of 200 people, each opening fifteen intranet pages per day, lost meaningful hours per week to the spinner.

That is the failure mode every wiki and every intranet gets wrong: waiting and clicking around. The two pains compound. Slow loads make people give up on the search bar and ask in chat instead. Asks in chat mean the answer never gets written down. The intranet that should have been the durable record becomes the place where last year’s policy silently rotted. The modern wiki — pages load in 50-150ms depending on your network — is what the durable half of the intranet should always have felt like.

The post-intranet world: federated focused tools

This is the slot the top-3 SERP universally skip. Almost every guide treats the monolithic intranet as the current reality and adds “modern features” on top — AI search, employee-experience analytics, push notifications. The working-team reality is different.

Most modern teams of 5-500 people now run something like:

A wiki for durable knowledge (onboarding, runbooks, ADRs, postmortems, decisions). The corporation wiki post and the knowledge management post cover the discipline side of this surface.
A chat app for ephemeral communication (Slack, Teams, Discord). The wiki holds the conclusions; chat holds the noise.
A file store for binaries that don’t belong in a wiki (Google Drive, OneDrive, Dropbox). Spreadsheets, design files, decks.
An identity provider for SSO (Okta, Google Workspace, Microsoft Entra). The auth layer the others sit on.
An HR / payroll system for employment records (Rippling, Gusto, BambooHR). A specialist application, not a folder in a wiki.
A ticketing tool for transient state (Linear, Jira, Asana). Tickets are work-in-flight; the wiki is what the work taught the team.

That federation is the modern intranet. It does not have a single URL. It has shared auth, a shared directory, and a shared sense of where each kind of artifact lives. The IT team’s job is to maintain the boundary and the federation; each tool does its part of the job.

Two quarters ago, an actual raccoon walked into our office through a propped-back fire door. Patches was the first to respond, butterfly net in hand. The incident was funny in person and reasonably funny in writing. The intranet detail that made the writing easier: the security playbook lived on a wiki page with an edit timestamp, the access-control map lived next to it, and the what to do if a non-employee enters the office page was searchable in seven seconds. The boundary the intranet is supposed to protect held; the durable half of the intranet — the wiki — meant the response was prepared, written down, and rehearsed. Wild raccoons are why the access boundary matters. Findable response procedures are why the wiki matters.

A quick history of the corporate intranet

The shape of intranets evolves in roughly six beats:

1990s — the LAN era. The intranet is a file share, a Lotus Notes database, and an internal-only website. Access is being in the building.
Early 2000s — the portal era. SharePoint launches in 2001; intranets become one big web app hosted by IT.
Mid-2000s — the wiki bolt-on. Confluence, MediaWiki, and others give the portal a writable surface that anyone can edit. The intranet starts to have user-generated content.
2010s — the social intranet. Yammer, Jive, Workplace, Microsoft Teams. The pitch is “the intranet, but a newsfeed.” Most deployments end up as half-used newsfeeds, with the wiki bit underneath still doing the durable work.
Late 2010s — the unbundling. Slack absorbs the ephemeral communication; SSO providers like Okta absorb the auth; Google Workspace and Office 365 absorb the files. The monolithic intranet starts looking like a bundle of services that could each be replaced.
2020s — the federation. Most working teams now run five-to-seven focused tools behind shared auth. The intranet is what the federation collectively does, not what any one tool ships.

The term intranet survives because the boundary survives. The shape of what sits behind the boundary keeps changing.

When you actually need an intranet (and when a stack of tools is enough)

Honesty section. Almost every team of more than three people needs the boundary — controlled access to internal resources. Not every team needs the monolithic portal.

Teams of 3-10: A shared password manager, a wiki, a chat app, and a file store behind SSO is most of an intranet. Skip the portal product entirely.
Teams of 10-100: Add an identity provider and a ticketing tool. The federation is now five tools. Still no monolithic intranet needed.
Teams of 100-1,000: Add HR, payroll, and probably a customer-support tool. The federation is now closer to ten tools. The IT team starts mapping who has access to what, but the portal product is still optional.
Teams of 1,000+ in regulated industries: Now the monolithic intranet earns itself — if compliance, audit, or a specific industry standard demands a single audited surface. Banking, healthcare, defence, regulated utilities. Outside those, federation usually wins.

Raccoon Page is the wiki half of a modern intranet, not the whole thing. We do not ship an SSO provider, an HR system, or a chat app — those are specialist tools, and your federation should use specialist tools for them. If your team’s pain is the wiki nobody opens, that’s our job. If your team’s pain is no shared identity provider or fragmented chat, fix those first; the wiki gets easier to adopt afterwards.

Things people actually ask

What is an intranet in simple terms? A private network inside a company that lets employees share information and collaborate without exposing it to the public internet. In practice, the word now usually means the small set of internal tools the company runs behind shared authentication.

What is the difference between intranet and internet? The internet is open to anybody with a connection; the intranet is closed to people outside one organisation. They use the same underlying technology (TCP/IP, HTTP). The boundary is the difference.

What is the difference between intranet and extranet? An intranet is restricted to one organisation’s employees. An extranet extends limited access to selected outsiders — customers, suppliers, partners — usually for a specific collaboration scope. Intra = within; extra = beyond.

What is an example of an intranet? A company’s internal wiki with onboarding docs, runbooks, and HR policies — accessed via single sign-on, not reachable from the public web. The wiki is the most visible part; the full intranet also includes the auth provider, the file store, the chat app, and the directory.

Is an intranet the same as a portal? Not quite. A portal is a single web app that aggregates information — often the intranet in the SharePoint era. An intranet is the broader concept of a private network inside an organisation; the portal is one possible shape of it.

Do small teams need an intranet? The boundary, yes. The portal, usually no. A four-person startup needs shared auth, a wiki, a chat app, and a file store — that is an intranet in 2026 terms. Skip the monolithic portal product until the team is well past 100 people.

Are intranets still relevant in 2026? Yes — but the shape has changed. The monolithic intranet portal has largely been replaced by a federation of focused tools sitting behind shared SSO. The concept is more relevant than ever; the product category has unbundled.

What features should a modern intranet have? Shared auth (SSO), an identity directory, a fast wiki for durable knowledge, a chat app for ephemeral communication, a file store for binaries, and clear which-tool-for-what ownership. The federation is the feature set.

Why are corporate intranets so slow? The traditional portal architecture is request-heavy — every page click triggers multiple upstream calls before anything renders. The fix is unbundling: a fast wiki for the durable content, dedicated tools for the rest. Pages should load in 50-150ms depending on your network, not seconds.

The intranet is older than most of the people who use it, and it has unbundled in the last decade into a federation of focused tools behind shared auth. We built Raccoon Page to be the wiki half of that federation — the durable knowledge surface that should never be the slow one. If you’re auditing a legacy intranet, the corporation wiki post covers the wiki-shaped piece, the knowledge management post covers the operating discipline, the digital workspace post covers the broader async layer, and the what is a knowledge base post covers the distinction between a knowledge base and a full intranet. Free for super-lean teams. No credit card required.