Already have the code?
Start there.
Use the Boombox developer kit from your own repository. Define the product outcome and keep your existing method, tests and domain standards.
A verified starting point.
Version 0.14.6 was installed and its local runner executed for the Boombox operating demonstration. This is an explicit tested pin, not a claim that it is the latest release.
npm install --save-dev --save-exact --ignore-scripts @konstantdotcloud/boombox@0.14.6
node ./node_modules/@konstantdotcloud/boombox/dist/boombox.js project init . --client codex --client claude --jsonInitialization installs the package’s project skill and returns local MCP connections. Use the returned commands in your coding agent. Start with: “Put this workflow on Boombox and get it running. Reuse the existing frontend and harness if they fit.”
Local work.
Connected authority.
Local inspection, validation and proof can proceed without a network credential. Connected operations require authentication, and deployment requires the relevant product-account authority.
A builder login does not grant access to company data or deployment resources. Optional evaluations, context and telemetry enrich the work independently.
Choose the supported product shape that fits the work: a repeatable capability, portable application or durable workload. Preserve the existing domain method and acceptance criteria.
Keep going.
Put one useful
slice into use.
A recurring decision. A method you already trust. An application with somewhere new to go.
Discuss your first deployment