Web evolution timeline from Web 1.0 through Web 4.0 with technological progression

Key takeaways

• The web moved from read, to read-write, to read-write-own, to read-write-execute. Web 1.0 (1991–2004) broadcast. Web 2.0 (2004–today) let users post. Web 3.0 (2014–today) let them own assets on-chain. Web 4.0 (2025–today) lets AI agents act on their behalf.

• Web 4.0 is the real commercial frontier right now, not Web 3.0. Gartner predicts 40% of enterprise apps will embed task-specific AI agents by the end of 2026, up from under 5% in 2025. Grand View Research puts the global AI market at about $540B in 2026. Analyst estimates for the Web3 market are $6–9B (2025), roughly 75 times smaller.

• “Web 3.0 = decentralised” is mostly a marketing story. Most dApps still depend on centralised RPC providers (Alchemy, Infura), gateway hosts (AWS, Cloudflare) and custodial wallets. Tim Berners-Lee’s Solid project takes a separate route to user-owned data, without a blockchain.

• Each era changed what “a software product” even means. Web 1.0 shipped brochures. Web 2.0 shipped platforms and SaaS. Web 3.0 shipped wallets and smart contracts. Web 4.0 ships autonomous agents, IoT swarms and context-aware ambient services.

• For a CTO hiring a partner today, the practical question is not “which Web are we on?” but “which capabilities belong in our stack?” This guide maps every era to the decisions, stacks, cost shapes and risks that matter when you scope a real product, and says when to chase each one and when to leave it alone.

Updated November 2026: a short answer to “what web are we in now”, OpenAI’s September 2026 agent launches, Gartner’s October 2026 agent forecasts, stablecoin supply for November 2026 and the EU AI Act content-marking deadline of 2 December 2026.

What is Web 4.0? The short answer

Web 4.0 is the fourth stage of the web, in which AI agents, connected devices and immersive interfaces act on a user’s behalf instead of waiting for clicks. Web 1.0 let people read, Web 2.0 let them write, and Web 3.0 let them own digital assets. Web 4.0 lets them delegate. You will also see it called the intelligent, agentic or symbiotic web.

No W3C standard defines it. The closest official definition is in the European Commission’s July 2023 initiative on “Web 4.0 and virtual worlds”: a web where artificial and ambient intelligence, the Internet of Things, trusted transactions and extended reality merge digital and physical objects into one environment.

Web 4.0 examples you can use in 2026

Agents that do the task, not just answer. OpenAI’s ChatGPT agent (July 2025) and agentic browsers such as ChatGPT Atlas (October 2025) fill in forms, compare offers and make bookings for the user. At DevDay in September 2026, OpenAI added computer use to its Agents API and introduced Dots: always-on agents in ChatGPT that keep working toward a goal between conversations.

Agents that pay. OpenAI and Stripe’s Agentic Commerce Protocol (September 2025), Google’s Agent Payments Protocol AP2 (September 2025) and Coinbase’s x402 (May 2025) let software agents check out and pay per request.

Agents that talk to tools and to each other. Anthropic’s Model Context Protocol (MCP) connects agents to tools and data, and Google’s Agent2Agent (A2A) protocol connects agents to one another. Both are now part of the Linux Foundation’s Agentic AI Foundation, which reached 305 member organisations in October 2026 (Linux Foundation).

Copilots inside products and ambient IoT. AI tutors in learning platforms, AI scribes on telehealth calls, and local models fed by the 21.1B connected IoT devices that IoT Analytics counted at the end of 2025.

Why Fora Soft wrote this playbook

Founders and CTOs don’t come to us asking for “Web 4.0”. They ask for a live streaming platform that has to scale to 20,000 concurrent viewers, an AI assistant that drafts lesson plans, an IoT hub for 500,000 edge devices, an intercom with face recognition, or a telehealth product under HIPAA. Each of those briefs belongs to a specific generation of the web, and each generation comes with its own tech stack, failure modes and cost shape. Get that framing right before the first line of code and you save yourself the next 18 months.

Fora Soft has been shipping web and video software since 2005. We built BrainCert into an e-learning platform used by global enterprises, delivered on-premise WebRTC for Nucleus, powered AI-driven sales video on Meetric, and developed the software for Blaze Streaming Media’s Volo, a live-event translation service. With that portfolio we have to think carefully about which web-era paradigm fits each product, and which ones are expensive hype we should steer clients away from.

This article is the internal cheat-sheet we use when scoping new projects, rewritten for a public audience. It compares the four eras on tech stack, user role, monetisation, developer effort and risk, the dimensions that decide buyer outcomes. Then it turns those differences into concrete choices for the product you are about to build.

Stuck choosing between an “AI app”, a “Web3 app” and a plain SaaS?

Bring the brief. In 30 minutes we will map it to the right era, the right stack and the right budget — no jargon, just the build we would actually take on.

Book a 30-min scoping call → WhatsApp → Email us →

The four webs in one sentence each

There are four web versions: Web 1.0, Web 2.0, Web 3.0 and Web 4.0. The simplest way to keep them apart: each generation added a new verb to what a user does on the web.

Web 1.0: read. Static HTML pages. Publishers wrote, everyone else consumed. HTTP, URLs and a browser were enough to deliver the product.

Web 2.0: read and write. Dynamic pages, APIs and databases turned visitors into contributors. The business model became “free product, your data is the price”.

Web 3.0: read, write, own. Public blockchains gave users cryptographic ownership of identity, money and assets with no platform in the middle.

Web 4.0: read, write, own, delegate. AI agents, IoT devices and edge compute act for the user, predict intent and coordinate across services. The human is no longer the one doing most of the clicking.

What web are we in now?

We are in Web 2.0 with a fast-growing Web 4.0 layer on top. The products most people use every day, from social networks and marketplaces to SaaS and streaming, still run on Web 2.0 architecture. AI agents that act for the user reached mainstream products in 2025 and 2026. Web 3.0 is live but narrow: it covers stablecoins and on-chain assets and is not the default way people use the web.

Reach for this framing when: a stakeholder pushes a buzzword (“we need a Web3 app”) before anyone has defined the product problem. Map the actual user verb (read, post, own or delegate), and the right era usually becomes obvious.

The four web eras side by side: Web 1.0 read, 2.0 write, 3.0 own, 4.0 delegate, each with its actor and core tech

Figure 1. The four webs at a glance. Each era added a verb (read, write, own, delegate) and a new kind of actor.

Web 1.0 vs 2.0 vs 3.0 vs 4.0 — the comparison matrix

This is the one table we pin at the top of every internal discovery doc. Use it to pressure-test a brief and find the column the product actually lives in. If two columns fight, split the scope.

Dimension Web 1.0 Web 2.0 Web 3.0 Web 4.0
Era 1991–2004 2004–today 2014–today 2025–today
User verb Read Read & write Read, write, own Read, write, own, delegate
Core tech HTML, HTTP, URLs AJAX, JS frameworks, REST/GraphQL APIs, cloud Blockchains, smart contracts, IPFS, wallets LLMs, vector DBs, edge AI, IoT protocols, agent frameworks
Typical product Brochure sites, directories, news portals Social networks, SaaS, marketplaces, streaming DeFi, NFT platforms, DAOs, wallet apps AI copilots, autonomous agents, ambient IoT, AR/VR
Monetisation Banner ads, paid licences Ads + data, freemium, subscriptions Token economies, protocol fees, NFT royalties Outcome-based pricing, per-action agent fees, micropayments
Dev complexity Low Medium–high High (security-critical) Very high (ML + real-time + distributed)
Signature risk Stale content, zero engagement Privacy, platform lock-in, moderation cost Scams, key loss, regulation Hallucination, bias, surveillance, energy cost

Most real-world products are a blend. A modern edtech platform like BrainCert is a core Web 2.0 SaaS with a Web 4.0 layer bolted on (AI tutoring, automated grading). A video surveillance platform is a Web 2.0 backend with a Web 4.0 edge-AI brain. The skill lies in knowing which layer carries the product’s actual value, and where to stop.

Web 1.0: the read-only web (1991–2004)

Web 1.0 is the first, read-only stage of the World Wide Web, roughly 1991–2004: site owners published static HTML pages and visitors could only read them. Sites had no accounts, comments or user posts. Typical Web 1.0 websites were info.cern.ch, the Yahoo! Directory, GeoCities home pages and the early catalogue pages of Amazon and eBay.

Tim Berners-Lee proposed the World Wide Web at CERN in March 1989. The first public website went live on 6 August 1991 at info.cern.ch. For the next decade the web worked as a giant distributed read-only library of static HTML, hyperlinks and a few images, with almost no interactivity.

What defined it

One-way publishing. Site owners wrote pages and visitors consumed them. There were no comment forms, no accounts and no user-generated content.

Minimal stack. HTML up to 4.01, CSS 1–2, HTTP 1.0, images in GIF and JPEG. The few dynamic pieces were Perl CGI scripts running on Apache.

Directory-led discovery. Yahoo!, AltaVista and later Google indexed pages; web rings and hand-curated lists covered most of the rest.

What it meant for software teams

One or two people could build a Web 1.0 product with an HTML editor, an FTP client and a shared hosting plan. Visual polish mattered more than interaction logic, and the skillset was closer to DTP and print design than to software engineering.

Reach for a Web 1.0 mindset when: you need a marketing site, documentation hub, regulatory filing archive or any asset where content rarely changes and speed and indexability matter more than interactivity. Static-site generators (Next.js SSG, Astro, Hugo) are the honest modern form of this era.

Web 2.0: the read-write platform web (2004–today)

Tim O’Reilly popularised the term “Web 2.0” in 2004. Facebook launched the same year, YouTube in 2005 and Twitter in 2006. The protocol stayed the same; the pattern changed. AJAX let pages update without a full reload, JavaScript became a real application runtime, and REST APIs let services compose. Users went from being the audience to being the inventory.

What defined it

User-generated content at scale. Posts, reviews, videos, likes. Wikipedia is the clearest proof that strangers with the right tools will build things.

Platforms, not pages. Value came from network effects rather than any single page: Facebook’s graph, YouTube’s catalogue, Uber’s two-sided marketplace.

Cloud, SaaS, APIs. AWS (2006), Heroku, Stripe and Twilio turned shipping a web product into an afternoon’s work instead of a data-centre contract.

Typical stacks today

LAMP / LEMP. Still powering half the internet. WordPress runs on LAMP, and Shopify grew up on Ruby on Rails on top of MySQL/PostgreSQL.

MERN / T3. MongoDB or PostgreSQL, Express/NestJS or Next.js API routes, React or Next.js, Node.js. It is the dominant SaaS stack today.

Real-time layer. WebSockets, WebRTC, Server-Sent Events. Video-heavy products (conferencing, live commerce, learning) add media servers like Janus, Jitsi and LiveKit next to the SaaS stack. We cover that pipeline in detail in our video and audio streaming services.

Where Web 2.0 pays off in 2026

Hype cycle aside, 95% of the profitable software businesses shipping today are still Web 2.0 at their core: vertical SaaS, marketplaces, streaming, collaboration tools. Our client portfolio shows the same picture. Sprii (live shopping), Ariuum (live debate) and Translinguist (video interpretation) are all Web 2.0 products architecturally, with AI features added at the edges.

Reach for Web 2.0 architecture when: the value is in multi-user workflow, content or marketplace liquidity, and you need a predictable compliance story (GDPR, HIPAA, SOC 2). 80% of the products we ship for clients sit here, with AI added selectively rather than used as the main engine.

Scoping a modern SaaS, marketplace or video platform?

Web 2.0 is still where most real revenue lives. We have 20+ years of pattern memory on scaling these products — let’s pressure-test your architecture before you commit.

Book a 30-min call → WhatsApp → Email us →

Web 3.0: the read-write-own decentralised web (2014–today)

Gavin Wood coined the term “Web3” in 2014 for an internet where ownership, identity and money run on public blockchains instead of corporate databases. The idea was to move trust from platforms to code.

What actually shipped

Bitcoin (2009). Permissionless digital money. It remains the only Web 3.0 product with clear, durable product-market fit at global scale.

Ethereum (2015). Turing-complete smart contracts. They enabled DeFi (Uniswap, Aave), NFTs (ERC-721, ERC-1155), DAOs and on-chain games.

Tooling layer. Solidity, Hardhat, Foundry, MetaMask, WalletConnect, IPFS, Ceramic, The Graph, Chainlink oracles.

Market reality. Analyst estimates put the Web3 / blockchain software market at $6–9B in 2025. After Bitcoin, the clearest product-market fit is stablecoins: about $291B in circulation on 9 November 2026, 61% of it USDT (DefiLlama). Stablecoins are real, but the software market around them is roughly 75 times smaller than the AI market it often gets compared with.

Where the narrative breaks

“Decentralised” is often centralised in practice. Most dApps rely on a handful of RPC providers (Alchemy, Infura), front-end hosts (Vercel, Cloudflare) and custodial wallets. When those fail, the “trustless” app fails with them.

UX is still brutal. Seed phrases, gas fees, chain switching and MEV make even simple flows painful for mainstream users.

Regulation is moving. In the EU, MiCA has applied in full since 30 December 2024, and the transition period for existing crypto-asset service providers ended on 1 July 2026. In the US, the GENIUS Act (July 2025) regulates payment stablecoins. The CLARITY Act on wider market structure failed a Senate cloture vote on 15 September 2026 (49–50) and is stalled, though a motion to reconsider keeps a later vote possible. In 2026, shipping a token-powered product is a legal project first and a tech project second.

Reach for Web 3.0 tech when: you need censorship resistance, real user-owned assets or programmable money, and you have in-house compliance counsel. If “a normal user log-in and a Stripe charge would also solve this”, you probably don’t need a chain.

The other path to ownership: Tim Berners-Lee’s Solid

Solid (Social Linked Data) is the answer from the web’s own inventor to the Web 2.0 data problem, and it deliberately avoids blockchain. Solid keeps user data in personal “pods” (online storage owned by the user) and lets apps request scoped access through linked data and open auth. It has more in common with a privacy-respecting OAuth + graph database than with Bitcoin.

For founders building a product where data portability matters, such as health, research, public sector or identity, Solid is an underrated alternative to shoehorning the stack onto a public chain.

Web 4.0: the read-write-own-delegate intelligent web (2025–today)

Web 2.0 put a page in your hand and Web 3.0 put a wallet in it; Web 4.0 puts an agent next to you. LLMs gave software a native conversational interface. IoT and edge compute gave it senses. Multi-agent frameworks let it orchestrate other services on your behalf.

The inflection came quickly. ChatGPT hit 1M users in 5 days in November 2022; OpenAI reported 900M weekly active users in February 2026 and said in August 2026 that ChatGPT had passed 1 billion. Grand View Research sizes the global AI market at $539.5B in 2026, up from $390.9B in 2025. Gartner expects 40% of enterprise apps to embed task-specific AI agents by the end of 2026, up from under 5% in 2025, and in September 2026 predicted that more than 10 billion autonomous agents will be clogging public services by the end of 2030. Put simply, any feature you build now has to assume an autonomous layer exists.

What a Web 4.0 product looks like

Copilots inside existing products. A writing assistant in Docs. A risk summariser in a claims tool. An AI coach inside a learning platform, the kind of feature we integrated into BrainCert and described in our AI integration playbook.

Autonomous agents. A negotiator that books travel inside a budget, an outbound SDR agent that qualifies leads, a maintenance agent that opens tickets against a fleet of devices.

Ambient & IoT. Smart buildings, precision agriculture, connected health. Devices feed signals to local models and coordinate through a cloud brain. IoT Analytics counted 21.1B connected IoT devices at the end of 2025 (up 14% year on year) and forecasts 39B by 2030.

Immersive layers. AR glasses, spatial video, mixed-reality training. We think about these product categories in our AR/VR practice.

The Web 4.0 stack, in practice

Foundation models. OpenAI’s GPT-5 and GPT-6 families, Anthropic Claude, Google Gemini, plus open-weight options (Llama, Mistral, Qwen) for cost, privacy or edge deployment.

Retrieval and memory. Vector databases (Pinecone, Weaviate, Qdrant, pgvector) for RAG; long-term memory layers for stateful agents.

Agent orchestration. LangChain and LangGraph, LlamaIndex, the Anthropic and OpenAI agent SDKs, the Model Context Protocol (MCP) for tool access, Agent2Agent (A2A) for agent-to-agent calls, AGENTS.md for instructions to coding agents, and increasingly custom in-house frameworks tied to the business’s tools. We document the same primitives in our guide to building production AI agents.

Edge and IoT. ONNX Runtime, TensorFlow Lite, NVIDIA Jetson, Google Coral; MQTT, CoAP, and HTTP/2 for device communication.

Observability and guardrails. Evaluation suites, PII filters, prompt-injection defences, content filters, audit logs, and a separate identity with scoped permissions for every agent. In regulated domains (healthcare, finance, legal, education) these are mandatory. Gartner put AI agent identity on its list of top strategic technology trends for 2027 (October 2026) and predicts that by 2028, 25% of enterprise security breaches will trace back to AI agent abuse.

Reach for Web 4.0 tech when: the core product value is “software that does work the user used to do” (drafting, reasoning, summarising, negotiating, triaging), or when devices and sensors are part of the product. Everything else is a Web 2.0 app with AI as a feature, not a Web 4.0 product. When the agent layer is the product, our AI integration and agent development team builds it on top of the stack you already run: tool access over MCP, evaluation suites and per-user cost ceilings from the first sprint.

Era-by-era tech stack cheat sheet

When a client asks “what will we actually build with?”, this is the compressed answer we share on the first call.

Layer Web 1.0 Web 2.0 Web 3.0 Web 4.0
Front end Static HTML, CSS React, Next.js, Vue, Svelte React + ethers.js, wagmi, RainbowKit Next.js + LLM SDKs, streaming UIs, Unity/WebXR
Back end Apache, Perl CGI Node.js, NestJS, Rails, Django, Go Solidity, Rust (Solana), Move Python + FastAPI, Node, agent orchestrators
Data Files on disk PostgreSQL, MongoDB, Redis, S3 Public chain state, IPFS, Arweave, Ceramic Postgres + pgvector, Pinecone, Qdrant, Weaviate
Real-time — WebSockets, WebRTC, LiveKit, Janus Chain events, The Graph, push oracles Streaming LLM responses, MQTT, CoAP
Infra Shared hosting, FTP AWS, GCP, Hetzner, Kubernetes, Cloudflare Alchemy, Infura, QuickNode, self-hosted nodes GPU clusters, inference services, Jetson/Coral edge
Identity None Email + OAuth, SSO, Auth0, Clerk Wallet address, ENS, SIWE, DID Hybrid identity + AI memory, per-agent scopes

Key events that define the four Webs (1989–2026)

Date Event Era
Mar 1989Berners-Lee proposes the World Wide Web at CERNWeb 1.0
Aug 1991First public website goes liveWeb 1.0
1995JavaScript invented; Amazon and eBay launchWeb 1.0
1998Google foundedWeb 1.0
2004Facebook launches; O’Reilly popularises “Web 2.0”Web 2.0
2005YouTube foundedWeb 2.0
2006AWS launches EC2/S3; cloud-native SaaS becomes defaultWeb 2.0
2008Bitcoin whitepaper releasedWeb 3.0
2014Gavin Wood coins “Web3”; Ethereum announcedWeb 3.0
2015Ethereum mainnet goes live; smart contracts shippedWeb 3.0
2017ICO boom; regulatory backlash startsWeb 3.0
2018Berners-Lee founds Inrupt around the Solid projectWeb 3.0 alt.
Nov 2022ChatGPT launches, 1M users in 5 daysWeb 4.0
2023GPT-4, Claude, Gemini; RAG and agent frameworks explodeWeb 4.0
2024Multimodal + voice models; first serious autonomous agents in productionWeb 4.0
2025ChatGPT agent and Atlas browser; agent payment protocols ACP, AP2 and x402; Gartner predicts 40% of enterprise apps will embed task-specific agents by end of 2026Web 4.0
Dec 2025Linux Foundation launches the Agentic AI Foundation with MCP, goose and AGENTS.mdWeb 4.0
2026ChatGPT passes 1B weekly users (Aug); EU AI Act transparency duties apply (Aug); A2A joins the Agentic AI Foundation (Aug); OpenAI ships Dots and computer use in its Agents API (Sep); AAIF passes 300 members (Oct); global AI market ≈$540BWeb 4.0

Mini case: turning a Web 2.0 video product into a Web 4.0 one

When we engaged on Meetric, the product was already a capable Web 2.0 sales video platform: record calls, share them, comment. The brief was to move it up the stack: detect when buyers hesitate, surface the moments that drove a deal forward, auto-summarise call outcomes into the CRM. It was a classic case of Web 4.0 layering on a Web 2.0 core.

The shape of the work was typical. Transcribe with Whisper-class ASR, extract entities and intents with an LLM, embed call chunks into a vector store for retrieval, produce summaries on a trigger. Latency-sensitive tasks went to smaller open models at the edge of our inference service; synthesis and reasoning went to frontier models. The Web 2.0 backend (video storage, auth, team permissions) did not change. We added a Web 4.0 brain on top of it.

How a Web 4.0 AI layer bolts onto an unchanged Web 2.0 core: call to ASR to LLM to vector store to auto CRM summary

Figure 2. On the Meetric mini-case, the Web 2.0 backend stayed put; the Web 4.0 layer went where humans did the cognitive work.

Most “AI transformations” we run in 2026 look like this. The Web 2.0 base rarely gets thrown away; the Web 4.0 layer goes where a human used to do cognitive work.

Want a Web 4.0 layer on your existing Web 2.0 product?

We have done it with video, edtech, health, and ops tools. Show us your product and we will sketch the smallest AI layer that actually moves a business metric.

Book a 30-min call → WhatsApp → Email us →

The market reality, in numbers

Most “where should we invest?” arguments come down to one comparison of size of prize, speed of growth and distance from mainstream adoption.

Market 2025 size Projection User scale
Global AI (Web 4.0)≈$390B≈$540B (2026), ≈$3.5T (2033) — Grand View ResearchChatGPT alone: 1B+ weekly users (Aug 2026)
IoT (Web 4.0 edge)21.1B devices39B by 2030 — IoT AnalyticsIndustrial + consumer fleets
Web3 / blockchain$6–9B (analyst range)Stablecoins in circulation: ≈$291B (Nov 2026, DefiLlama)Hundreds of millions of wallets, far fewer active
Global SaaS (Web 2.0)≈$299B (Gartner, end-user SaaS spend)Growing about 19% a year (Gartner)Billions of B2B seats
Static web / CMS (Web 1.0 legacy)n/aStill powering >40% of all sites (WordPress et al.)Global audience
2026 market size bars: global AI about $540B vs SaaS about $299B vs Web3 $6-9B; AI is roughly 75x the Web3 market

Figure 3. Market size, 2026: by analyst estimates the AI (Web 4.0) market is roughly 75 times the Web3 market.

A decision framework — pick the right era in five questions

Before you hire an agency, answer these five questions in writing. Taken together, the answers show which web your product really needs.

Decision tree for picking a web era by primary actor and value: AI agent, owned asset, workflow, or static content

Figure 4. A five-question decision tree: the first “yes” names the era that carries your product’s core value.

1. Who is the primary actor? A human reading? A human posting? A human owning an asset? An AI agent acting for the human? The answer names your era.

2. Where does the value accrue? In content (1.0), in network effects or workflow (2.0), in user-owned assets (3.0), or in cognitive work performed by software (4.0)?

3. What is your regulatory surface? GDPR and SOC 2 are Web 2.0 concerns. MiCA and securities law are Web 3.0 concerns. EU AI Act, model risk, data provenance and content provenance are Web 4.0 concerns: the Act’s transparency duties (telling users they talk to AI, labelling synthetic content) apply from 2 August 2026, and the 2026 Digital Omnibus (Regulation (EU) 2026/1744) moved high-risk obligations to 2 December 2027 for Annex III systems and to 2 August 2028 for AI inside regulated products (Annex I). Generative systems already on the market have until 2 December 2026 to mark synthetic content. Plan for the one you cannot ignore.

4. What is your latency budget? Sub-100ms user actions push you toward the edge (Web 2.0 real-time, Web 4.0 edge AI). Minute-scale reasoning is fine on frontier LLMs. Block-time latency is acceptable only for true Web 3.0 use cases.

5. How long must this run? A marketing site lives 2–5 years. A SaaS 10–20. A protocol, if it works, forever. A Web 4.0 product depends on model generations you cannot control. Pick the commitment you can actually fund.

Five pitfalls we see teams repeat

1. Chasing the label, not the capability. A project badged “Web3” or “AI-native” to satisfy investors, but whose user problem is solved better by a plain Web 2.0 app with good caching and a boring database. You pay for complexity you will never need.

2. Treating decentralisation as free. Running your own indexers, RPC nodes and signers is real ops work. Delegating to Alchemy/Infura is centralisation in a costume. Budget for one of the two; do not assume both.

3. Treating AI as free. Token costs compound. A chat UX that looks cheap at demo scale can cost six figures a month at production scale. Measure cost-per-request from day one; design prompts, context windows and model routing for unit economics.

4. Skipping evaluation suites. Web 4.0 products break silently: hallucinations, drift, prompt injection, output format regressions. Without automated evals you will ship regressions to production and not know for weeks.

5. Ignoring the Web 2.0 basics. Auth, permissions, observability, billing, audit logs, customer support. Every Web 3.0 and Web 4.0 product we have seen die in production died from weak Web 2.0 plumbing underneath.

KPIs to measure, per era

Quality KPIs. Web 2.0: page-load p95 under 2.5s, WebRTC packet loss under 2%, API error rate under 0.5%. Web 3.0: failed-transaction rate under 1%, signer availability over 99.9%. Web 4.0: task success rate (human-evaluated) above 90%, hallucination rate under 2% on guarded tasks, prompt-injection defence coverage 100% of user-input surfaces.

Business KPIs. Web 2.0: activation rate, weekly active users, net revenue retention above 110%. Web 3.0: unique wallets transacting, protocol fees, TVL. Web 4.0: cost-per-successful-task, tasks completed per user per week, deflection rate of human work.

Reliability KPIs. Web 2.0: uptime 99.95%, MTTR under 30 minutes. Web 3.0: node availability, re-org tolerance. Web 4.0: model provider fallback coverage, degraded-mode availability (works without AI when the AI is down).

When to say no to the next Web

Don’t use Web 3.0 when: there is no censorship-resistance requirement, no genuinely user-owned asset, and no regulator asking for on-chain proof. A permissioned Postgres table and a Stripe link beat a chain for 90% of SMB use cases.

Don’t use Web 4.0 (autonomous agents) when: the cost of an error is catastrophic and non-reversible (executing irreversible financial trades, releasing medical treatments, moving heavy machinery) and you cannot fund the evaluation suite and human-in-the-loop work that makes it safe. A human-in-the-loop Web 2.0 workflow with AI suggestions is often a better product.

Don’t push AI to the device edge when: your devices are not shipping yet, your SKUs are in flux, or your connectivity is reliable enough to keep inference in the cloud. You can always push inference to the edge later; you cannot un-ship bricked firmware.

What this means for the next product you ship

The tempting mistake is to pick an era and try to stay inside it. The products that win in 2026 sit on three layers at once: a Web 1.0 surface for content and SEO, a Web 2.0 core for identity, workflow and billing, and a selective Web 4.0 layer where AI actually deflects work. Web 3.0 shows up only where it is legally, commercially or technically irreplaceable.

Modern product stack: Web 1.0 content surface, Web 2.0 core engine, a selective Web 4.0 AI brain, Web 3.0 only if needed

Figure 5. Winning products stack all four eras: a Web 1.0 surface, a Web 2.0 core, and a selective Web 4.0 brain.

If you are building or maintaining a software product right now, the task is to compose capabilities from all four eras around one specific job your customer needs done, rather than to pick a “web”. Our product planning practice turns that composition into a 12–16 week plan with real numbers on it.

FAQ

What is Web 4.0 in simple terms?

Web 4.0 is the web where software acts for you. Instead of reading pages (Web 1.0), posting (Web 2.0) or holding crypto assets (Web 3.0), you hand a goal to an AI agent or a connected device and it does the clicking, comparing and booking.

What web are we in right now?

In 2026 we live on a Web 2.0 base with a Web 4.0 layer spreading over it: AI agents and copilots now sit inside everyday products, but accounts, feeds, payments and data still run on Web 2.0 platforms. Web 3.0 is used mainly for stablecoins and on-chain assets.

What are examples of Web 4.0?

In 2026: AI agents that complete tasks in the browser (ChatGPT agent, ChatGPT Atlas), agent payment protocols (ACP, AP2, x402), copilots inside SaaS products, AI scribes in telehealth, and IoT fleets that run models at the edge.

When did Web 1.0 start and end?

Web 1.0 started with the first public website, info.cern.ch, on 6 August 1991, and is usually said to end around 2004, when Tim O’Reilly popularised the term “Web 2.0” and Facebook launched.

Is Web 4.0 officially defined anywhere?

There is no single standards body that has stamped a Web 4.0 spec the way the W3C specified HTML. The European Commission defined it in its July 2023 initiative on “Web 4.0 and virtual worlds” as a web that merges digital and physical objects through artificial and ambient intelligence, IoT, trusted transactions and extended reality, and Gartner and Frontiers research now regularly treat autonomous AI agents plus IoT plus ambient computing as the defining features. In practice, “Web 4.0” is shorthand for a cluster of real technologies that already ship, rather than one standard.

What is the difference between Web 3.0 and Web3?

Historically, “Web 3.0” referred to Berners-Lee’s semantic web: machine-readable data and linked data standards. “Web3” (one word) is Gavin Wood’s 2014 reframing around public blockchains and crypto-assets. In 2026 most people use them interchangeably, but the original semantic-web vision now lives on more clearly in Solid and linked data projects than in crypto.

Is Web 4.0 the same thing as the metaverse?

Not quite. Immersive and AR/VR interfaces are part of the Web 4.0 experience, but the defining feature is autonomous intelligence, meaning software that acts for the user. A Web 4.0 product can live entirely in a 2D browser with an AI agent; it does not need a headset. The metaverse is one possible Web 4.0 interface, not the definition.

Should my startup pick Web 3.0 or Web 4.0 first?

For 90% of startups we see, Web 4.0 is the better bet in 2026. The AI market is roughly 75 times larger by analyst estimates, the buyer is already budgeting for AI, and the time-to-value is weeks instead of quarters. Web 3.0 is correct when censorship resistance, user-owned assets or programmable money is the product itself rather than a decoration on it.

Does Web 4.0 replace Web 2.0 stacks?

No. Web 4.0 sits on top of Web 2.0 as a layer and does not replace it. Auth, billing, multi-tenant data, real-time features and compliance are all still Web 2.0 engineering. AI and autonomous agents live on top, calling Web 2.0 services the same way humans do.

How do I avoid runaway AI costs in a Web 4.0 product?

Four levers work in practice: route simple prompts to small/local models and reserve frontier models for hard tasks; cache responses aggressively for stable queries; constrain context windows with retrieval instead of stuffing; and set hard per-user cost ceilings that degrade gracefully when hit. Our engineers typically build these controls in from the first sprint instead of leaving them for a later optimisation pass.

Is it a bad idea to still build a “Web 1.0” static marketing site?

Not at all. It is actively good. Static sites built with modern SSGs (Next.js, Astro, Hugo) are fast, cheap to host, search-friendly and easy to maintain. Most companies over-engineer their marketing sites. A “Web 1.0” mindset for content + a Web 2.0/4.0 stack for the product is often the right split.

How does Fora Soft scope a multi-era product engagement?

We start with a 30-minute call, then do a 1–2 week discovery that produces a tech stack map (by era), a risk register, and an MVP plan with a real number. Accelerated by our internal AI tooling, this usually runs faster and leaner than traditional discovery at larger agencies. We say so up-front instead of padding timelines.

Web 4.0 in practice

How we improve software products with AI features and components

The internal playbook for adding a Web 4.0 layer to an existing Web 2.0 product without rebuilding it.

Web 4.0 vertical

The future of AI in video streaming

Where autonomous intelligence changes one of the web’s highest-bandwidth categories.

Web 2.0 at scale

Future live streaming trends for 2025 and beyond

The real-time backbone every modern product depends on — what changes in the next two years.

Product planning

How wireframing saves time in app development planning

The step before you pick a web era — turning a brief into a concrete product shape.

AI + growth

The essential guide to AI-powered SEO

What “Web 1.0” content looks like when AI agents are the ones reading it.

Ready to build for the web that is actually here?

The internet did not leap from Web 1.0 to Web 4.0 by replacing layers. It kept them. Every product that matters in 2026 is a careful stack of static content, Web 2.0 workflow, occasional Web 3.0 primitives, and a Web 4.0 brain where it moves the numbers. The teams that win stop arguing about labels and compose capabilities on purpose.

If you have a product idea, an existing platform, or a stuck roadmap, bring it to a 30-minute call. We will tell you which era your real problem lives in, what the honest cost shape looks like with Agent Engineering built into our delivery, and which parts of the stack are worth writing and which are not.

Book cover: AI for Video, Volume 6 of the Fora Soft Video Engineering HandbookBook cover: AI for Video, Volume 7 of the Fora Soft Video Engineering HandbookBook cover: Video Streaming, Volume 3 of the Fora Soft Video Engineering Handbook

The handbook · 7 volumes

Fora Soft Video Engineering Handbook

If your answer to the five questions is Web 4.0, the product you ship is one where AI agents see, hear and act inside live video and voice. We wrote a seven-volume handbook on that stack; start with the volume on real-time AI pipelines, agents, serving and cost, then read the AI capabilities volume and the WebRTC and delivery volume that the agents ride on. Written by Nikolay Sapunov, CEO at Fora Soft.

Browse the handbook on Amazon →7 volumes · 9,000+ pages · Kindle & paperback

Have a custom software idea? Let’s build it together.

One call, three answers: what era your product lives in, what we would actually build, and what it costs when a senior team ships with AI-assisted engineering from day one.

Book a 30-min call → WhatsApp → Email us →

  • Technologies