Skip to article
Public docs

Shiplet documentation

Publish on managed hosting, review safely, revise portable packages, and understand exactly where code runs and who owns it.

Browse documentation
Start

Introduction

Prepare, review, revise, and own portable application packages with Shiplet.

Shiplet turns a build output, static export, standalone file, or public preview URL into a shareable review experience, then keeps feedback and immutable revision history attached to one stable Shiplet.

Open the Shiplet app to prepare a managed static review. No Cloudflare account is required.

Choose your task

Managed publish and review → Fork and validate immutable revisions → Optionally deploy to your Cloudflare.

Start on managed hosting. Infrastructure ownership is a later choice, not a prerequisite for publishing or review.

One application, clear ownership

A package may contain artifact files, a custom review widget and workflow, revision-scoped MCP handlers, agent instructions, validation declarations, requested capabilities, and provenance. Shiplet's trusted kernel keeps identity, access policy, human attribution, audit history, activation, secrets, state, limits, and deployment authority outside that package.

Package snapshots become immutable revisions. To change one, fork an isolated draft, update it, validate it, and explicitly promote it. The active revision never edits itself in place.

The public automation path is Code Mode MCP or direct REST. The source-checkout CLI remains limited to authorized repository contributors.

The kernel always exposes two stable MCP tools, search and execute. A package may also declare revision-scoped custom tools that cannot shadow kernel tools.

Next: prepare your first managed review artifact. The OpenAPI document is the machine-readable contract for documented public REST operations; browser-only product management journeys remain in these guides.