What's underneath PhiWebs — PWFabric.
PhiWebs is where your living pages live. PWFabric is the engine underneath it — the layer that makes "Say it. Approve it. It's live." safe enough for real work.
PWFabric makes PhiWebs possible. It isn't a product you use directly; it's the ground every product is built on — the physics of the platform.
Your page is data, not code.
What PhiCo produces is a Surface — a living page whose layout, styling, and behavior are held as data, not a code bundle. That's why it can change at any moment, and stays inspectable, versioned, and portable.
Edited any time
No build, no redeploy — a change is live the moment it's approved.
Inspectable at every point
The structure is visible and explainable at all times. There is no compiled, unreadable layer between what you asked for and what shipped.
Versioned by default
Every save is a kept version. The history always stays; return to any past state in one click.
Portable
Export it, share it, install it into another workspace. A page born in one place runs in another.
Open to everyone
Not just developers — anyone on the team can build. Ready-made parts and your approval keep that door both open and safe.
AI velocity, auditable control.
Ungoverned AI output brings speed and takes away control. PWFabric grounds the AI in three things: real parts, your approval, and kept versions. Speed doesn't cost you control.
Built from real parts
PhiCo builds only from reviewed Blocks — cataloged, ready-made parts. It can't invent a part that doesn't exist; everything it proposes is publishable.
Approved before it ships
Every change — human or AI — arrives as a Receipt: an itemized list of exactly what will change. You review it, then approve or reject. What ships is what you reviewed.
Nothing is lost
Every publish is a kept version. Return to any previous one in one click — experiments are cheap when nothing is lost.
A World for every customer.
A World is your isolated workspace, with its own identity, plan, members, data, rules, and storage. Worlds don't share a common infrastructure layer.
Everything is yours
Identity, plan, members, data, rules, storage — all of it lives only in your World.
No shared layer
Worlds are isolated from each other by design. None can see or reach another's data.
Traceable end to end
Every change leaves a trail. Per-World records mean the answer to "who changed what, and why" is always at hand.
Knowledge that travels.
The ecosystem wasn't bolted on. A solution or part you build is packaged once and installed anywhere — the platform's own parts go through the same line.
Package once
Wrap a page or part into a pwpack — a signed, installable bundle — and anyone can install it into their own World.
Symmetric authorship
First-party and community packs go through the same publish line. No privileged path, no second-class plugins.
Knowledge ships with the pack
Know-how travels inside the pack. PhiCo learns how to use a part from the pack itself; as the marketplace grows, so does the shared knowledge.
See what's installable today in the marketplace or publish packs of your own as a publisher.
AI cost stays visible.
Every AI job — building, generation, review — is metered in credits. You see what was spent and what it produced.
A credit is a unit of measurement: AI usage in your World stays visible, bounded, and traceable.
AI credits
Every AI operation in your World is metered in credits — included in every plan; top up when you need more.
The full contract is written down.
Schemas, the SDK, the publish line, the runtime — all of it is in the developer docs. Read them, or open a World and start building.