Public
Publish to the catalog. Anyone with Construct can install. Reviewed for safety, signed for integrity, ranked by usefulness — not by promotion.
Marketplace
An app store for AI-native work.
Install Spaces for every workflow. Build your own and ship them to the world, to your org, or to a single project. Same OS underneath, same Operator inside, same SDK to build.
Screenshot needed
The marketplace inside Construct. Left rail: categories (Productivity, Business, Operations, etc.). Main grid: Space cards with icon, name, version, short description, install button. Mix of installed and not-yet-installed Spaces. Top filter: All / Installed / Updates available. Search at the top. Same shot you'd reuse on the home page if needed.
/shots/marketplace-catalog.pngDistribution
Three audiences, one artifact.
A Space ships the same way regardless of who sees it. The reach is a publish-time choice, not a re-build.
Private
Distribute inside your org only. Internal tools, company-specific workflows, proprietary processes. Members install with one click; nobody outside ever sees it listed.
Scoped
Pin a Space to a single project. Travels with the project, comes and goes with its lifecycle, no install required for collaborators on that project.
Categories
If a workflow deserves software, it can be a Space.
Some of what's already in the catalog. The set grows weekly.
ProductivityBusinessOperationsSalesSupportEngineeringDesignFinanceHealth & FitnessEducationCommunicationReferenceLifestyleUtilitiesGames
Trust
Open catalog, closed loopholes.
An open marketplace works only if the install is safe. Four guardrails make that real.
Signed manifests
Every published Space is signed by its publisher. Construct verifies the signature on install and at every update.
Capability declarations
What a Space asks for is what you grant. Files, network, tools, automation — declared up front, never escalated by prompt.
Reviewed before public
Public listings go through a safety review. Air-gap, telemetry, network egress, and prompt-injection surfaces all checked.
Versioned and revertable
Each install pins a version. Updates are opt-in by default; revert in one click if a release breaks something.
Publishing
Ship a Space in four steps.
Same flow we use to publish Construct's own built-in Spaces. The CLI handles the boring parts.
- 01Scaffold`construct scaffold my-space` — manifest, capabilities, icon, basic Operator wiring.
- 02BuildEdit code in your local Construct, or open SpaceKit for a guided flow. Live preview in a sibling window.
- 03Sign`construct publish` signs the build with your publisher key. The marketplace verifies the signature on every install.
- 04ShipPick the audience: public catalog, private to your org, or scoped to a project. Same artifact, different reach.