Publish the packs teams ask for.
Bundle a component, a feature, or a whole solution as a pwpack — a signed, installable package — and publish it to the marketplace through the same pipeline our own packs travel. Once listed, teams install it into their Worlds (their isolated workspaces), and PhiCo builds pages with it.
1export default defineBlock({ 2 id: 'team/pricing-table', 3 schema: pricingSchema, 4 render: PricingTable, 5}) 6 7// manifest.json — what PhiCo reads 8{ "kind": "block", "ai": { "composable": true } }A Block — the ready-made part pages are built from — is plain TypeScript plus a manifest. If you can write a React component, you can publish a pack.
One pipeline. No second-class lane.
Your pack travels the same path as a first-party one: authored, described, packaged, reviewed, listed. The platform's own components go through these exact steps.
- 01
Author
Write your component with defineBlock — a typed schema and a React render. Real code, a real component.
- 02
Describe
The manifest tells PhiCo what the component is and how to use it: props, data needs, and an AI knowledge brief that travels with the pack.
- 03
Package
Bundle components, features, and pages into one pwpack — a single signed, versioned unit.
- 04
Reviewed
Every submission passes human review before it reaches a customer World — the same bar our own packs clear.
- 05
Listed
Once approved, your pack is listed on the marketplace. Teams install it; PhiCo proposes your components alongside ours.
Write it once. It works everywhere.
The same pipeline as first-party
Your packs publish through the same pipeline PhiMajor uses for its own — every release signed and versioned. Not a path added on later.
Listed means reviewed
Every pack passes human review before it reaches a customer. When yours is listed, it's known to have cleared the same bar ours did.
PhiCo builds with your components
Each component ships with a manifest the AI reads. In the World where it's installed, PhiCo proposes your components the way it proposes ours — no integration work on the customer's side.
Plain TypeScript, a real SDK
Write with defineBlock, describe with a manifest, package, submit. No closed runtime to learn — if you know React, you're ready.
Paid packs and revenue share — on the roadmap
A solution built once, installed everywhere.
Bundle any solution as a pack and it goes to the marketplace. Others install it into their own Worlds, build on it, repackage it — the catalog and the shared knowledge grow together.
Write once, distribute everywhere
A component, a feature, or a whole solution becomes a portable pwpack. It installs into any World, on any channel — web, embed, Teams, mobile.
Symmetric authorship
First-party and community packs share one publish pipeline. There is no privileged path; there is one catalog everyone draws from.
Knowledge ships inside the pack
Knowledge briefs travel with your pack; PhiCo learns how to use what you built from the pack itself. Your expertise compounds in every team that installs it.
Tell us the pack you have in mind.
The catalog is young; early publishers shape what teams find first. Write to us about what you want to build.