FULL-STACK TYPESCRIPT · AGENT-READY BY DESIGN

Build applications that understand themselves.

PipWeb models capabilities, surfaces, flows, trust and runtime policy as one application graph, so humans, APIs and agents all operate on the same architecture.

0.3.0-alpha.1020 private framework packagesNode 24+React 19
PIPWEB / APPLICATION GRAPHLIVE
DECLAREroutesactionsflows
PIPWEBGRAPH
EXPOSEWEBAPIAGENT
20Framework packagesPublished privately at alpha.10
3Primary surface typesWeb · API · Agent
0Audit findingsLatest framework audit pass
1Canonical graphCapabilities, surfaces and flows

THE IDEA

Stop treating the application as a pile of routes.

Traditional frameworks organise files. PipWeb organises intent.

You declare what the application can do, how that capability is exposed, who may invoke it, and what evidence should exist around execution. The runtime then has enough context to inspect, govern and explain the system.

APPLICATION GRAPH

One model. Multiple ways in.

The graph keeps human interfaces, APIs and machine callers aligned around the same capability contracts.

DECLAREroutesactionsflows
PIPWEBGRAPH
EXPOSEWEBAPIAGENT
01Declare capabilities

Describe application intent independently of transport or rendering.

02Expose surfaces

Connect web, API and agent entry points deliberately.

03Inspect the system

The graph becomes machine-readable architecture for tooling and governance.

FULL STACK, WITHOUT THE MYSTERY

Every layer has a job.

PipWeb keeps routing, capability intent, trust, durable execution and infrastructure adapters separate enough to reason about, but connected enough to operate as one framework.

01SURFACES

Web · API · Agent

02CAPABILITIES

Intent · Contracts · Policy

03FLOWS

Retries · Idempotency · Compensation

04TRUST

Principals · Entitlements · Approval · Audit

05RUNTIME

SSR · Cache · Uploads · SSE · WebSockets

06ADAPTERS

Postgres · Valkey · NATS · S3 · OpenTelemetry

GOVERNED EXECUTION

Agents do not get a side door.

Sensitive actions can require identity, entitlement, policy checks, human approval and auditable execution receipts.

01
PrincipalWho is acting?
→
02
PolicyAre they allowed?
→
03
ApprovalDoes a human need to approve?
→
04
ExecuteRun the capability.
→
05
ReceiptRecord governed evidence.
The point is not more ceremony.

The point is that the runtime knows enough about an action to treat a browser click, an API request and an autonomous agent consistently.

COMING FROM NEXT.JS?

Migrate the architecture, not just the files.

PipWeb's migration tooling scans existing structure, builds a semantic plan, generates PipWeb-native scaffolding and verifies the result before cutover.

01SCAN

Inspect routes, layouts and framework bindings.

02MAP

Create a semantic migration plan.

03CONVERT

Generate PipWeb-native application structure.

04VERIFY

Build, inspect and audit before cutover.

DOGFOODING

This site is built with PipWeb.

It installs the private alpha.10 packages, renders with the PipWeb runtime, serves its own SEO endpoints and is used as a production acceptance application for the framework.

CURRENT STATUS

Production-capability alpha

Core framework gates are green. We are using PluginPip-owned applications to find the remaining rough edges before wider developer adoption.

See current capabilities →

BUILD DIFFERENTLY

Make the application graph the centre of the system.

pipweb create my-product --template product