How it works · the mechanics
From edition to your product.
Start from a cohesive edition with useful defaults, shared implementations and tests. HappyToHelp is the first launch. Run it yourself with the edition instructions, keep it in your accounts with Assisted, or request Managed operation.
Choose. Adapt.
Keep improving.
Use the selected edition’s README and operating description for actual commands and prerequisites. Standalone keeps execution local to your accounts; Assisted connects customer Cloudflare and GitHub; Managed uses the operator cloud and private repository. Hosted qualification remains pending.
Pick a seed
Read the edition’s purpose, contract, acceptance status and operating requirements before deploying. Requirements describe the intended outcome; release evidence shows what has been verified.
Machine face on every listing: raw seed.json, CONTRACT.md, and the edition README.
- license
- MIT
- contract
- CONTRACT.md, requirements and coverage
- baseline
- BASELINE.md, twenty-two shared clauses
- externals
- declared, each with a reason
- operatingCost
- the plan the default stack needs
Listings are generated from product artifacts. Check their recorded release identity and known gaps.
Connect your cloud
For Assisted, the customer chooses the Cloudflare account and GitHub repository where the source and application live. For Managed, the operator cloud and private repository hold the running service.
Standalone owners use an ordinary source checkout and the product’s own deployment instructions. HappyToHelp’s public source and installation guide are available.
The recommended foundation uses Cloudflare; owners may adapt the infrastructure. Review the selected edition’s actual prerequisites before connecting an account.
- Workers — deploy and manage the seed's Worker
- D1, R2, Queues — create the storage the seed declares
- Account read — find the account to deploy into
Illustration only. The actual permissions and account selection appear in Cloudflare’s authorization screen.
Get your live URL
A qualified Assisted path copies or updates source in the customer repository, configures the app, and presents its resource plan and build evidence before publishing approval. Managed uses the operator service path; neither hosted path is open yet.
Cloud and external-service costs depend on the edition and usage. Read its declared dependencies and verify current provider requirements before deployment.
Illustrative deployment destination and resource types. The selected edition declares its actual resources.
The ownership boundary
Standalone and Assisted keep the deployment and source in customer-controlled accounts. Managed uses the operator cloud and private repository. The lists below explain the custody boundary; check each path's current availability before enrollment.
- The source, MIT, and the fork it lives in — take it at any time
- The Cloudflare account, and every resource provisioned inside it
- Your data: D1 rows, R2 objects, every attachment
- The domain, and where the thing is reachable
- Every customisation you or your agent make to the code
- The deploy credential — a scoped API token minted in your account, revocable by you
- Assisted: your fork's git history, to land a verified release onto it
- Assisted: the Cloudflare API and GitHub grant you choose to connect
- Managed: the operator cloud and private repository that run the service
- Each path: only the declared deployment and update access, with a recorded exit path
Independent operation, data recovery and revocation are requirements for the managed service. Claim them as verified only for a release with corresponding evidence.
Any future credential custody needs limited scopes, isolation, secure storage, revocation and an audit trail.
Updates that land over your changes
Your local Codex or Claude CLI can apply update instructions to the checkout you own without drawing on a service’s management/update AI allowance; any provider charges for that local work remain yours. A paid path can prepare the same work for the selected custody model. Included credits are available for management and update AI work; there is no automatic overage, and additional paid work needs your approval. In every case, your agent compares upstream changes with recorded owner intent, then verifies the result and existing-data transitions.
Standalone · local CLI
Assisted or Managed · service path
- Standalone
- Use Codex or Claude locally in the edition checkout. Provider and AI costs are yours to pay directly.
- Assisted · $10/mo
- Keep Cloudflare, GitHub and selected external provider billing and keys in your name. The plan includes an available $5/mo allowance for management and update AI work; enrollment is available.
- Managed · $100/mo
- The service price includes operator cloud and private-repository operation. Edition and customer-facing AI or selected external services use separate provider billing and keys where required; the plan includes an available $50/mo allowance for management and update AI work.
The developer path
An edition is an ordinary source repository. First-party authors, owner forks and community publishers use the same authoring inputs. HappyToHelp’s first launch keeps local CLI work and service-managed work on the same source and verification path.
Your repo, your org
Clone, branch, change and publish your edition using ordinary Git. Choose the release and source inputs appropriate to your product.
Deploys stay the seed's own
Read the edition’s actual workflow and operating description. Deployment commands and automation vary across products and releases.
Updates as pull requests
An agent can prepare a pull request with the change, affected requirements, migration work and verification evidence. Assisted and Managed hosted delivery remain subject to launch qualification.
Edition source commands
Use the selected edition’s own source-authoring and product commands. Other products retain their own tooling; use their README.
Firing us
A qualified paid service must let owners recover source and data, revoke access, and continue operating independently. For Managed, management, update and new-deployment authority ends at the paid-period boundary; operator resources enter a documented export, handover and manual-retirement window of at least 30 days. Existing runtime is not promised to continue, while Standalone and Assisted resources remain in the customer accounts that own them.
Leaving must preserve a working product. Optional management should earn its price through useful improvements and convenience.
Written for your agent, not just for you
Read the edition’s agent guidance, contract, acceptance record and intentional differences. Requirements and tests help the agent preserve what matters; missing coverage remains visible.
- AGENTS.md
- How to work on the edition: authoritative source, requirements, intentional differences and actual checks.
- CONTRACT.md
- Recorded product requirements, with actual coverage and unmet obligations reported separately.
- BASELINE.md
- Applicable baseline requirements, including independence, export, retention and audit.
- seed.json
- The manifest: externals, operating cost, resources, verified release history.
When an update stops red
General-purpose improvements we have rights to publish become common source and tests, adopted in actual products. Private customer code and data stay private. Further fixes improve that shared implementation, and deeply rewritten editions can participate through their agents.
Pick one. Own the result.
HappyToHelp is the first launch target. Choose standalone, Assisted or Managed after checking the current release status.