Your customers ask for things even your app store can't ship.
If you already have APIs, an app marketplace, and a developer program, you've solved 80% of extensibility — the parts that scale. Forge handles the other 20%: custom, per-customer features no third-party developer will build because the audience is one company. A new tier alongside your marketplace, not a competitor to it.
A new layer in your existing extension stack.
Your platform already has tiers of extensibility. Forge adds one more — the per-customer custom layer that today either gets built by your services team, by the customer's own engineers, or never.
Your platform team
Core product, big features, generic capabilities used by every customer. Scales to all of them.
Your marketplace
Third-party developers ship apps generic enough to monetize across many customers. Scales to a segment.
Forge
Per-customer codegen for the long tail no third-party will build because the audience is one company.
Not a marketplace replacement. A complement.
Marketplace apps are generic and broadly useful — Forge extensions are specific and narrowly useful. Different volume per extension, different unit economics, different audiences. Marketplace apps stay where they belong; Forge fills the gap below them. No new dev program for you to run; the build-time agent uses the same APIs your marketplace developers already use.
Built on the same primitives your dev program already trusts.
Forge introspects your existing MCP / OpenAPI / GraphQL surface — the one your marketplace developers already use — and exposes it to the build-time agent. Every extension runs in a sandboxed per-customer namespace, with HMAC-signed dispatch and isolated secrets. The same isolation guarantees you'd require of any third-party app, applied to per-customer codegen.