docs: hosted pricing tier proposal (#17)#61
Merged
Conversation
Concrete launch proposal for the four tiers named in HOSTED.md: Community (self-host, free), Hosted Starter ($99), Hosted Team ($399), Hosted Dedicated (from $2,000/yr-billed). Flat monthly + daily task caps, BYOM at every tier, no usage billing until cost distribution is known. Every promised limit maps to an enforcement mechanism that already shipped (#3 tenancy, #5 isolation, #6 memory, #7 routing, #11 gates, #15 caps and metering, #12 retention), so the price sheet cannot drift ahead of the product. Open decisions (exact figures, trial policy, OSS discount) are listed for the maintainer call — this is the documented proposal the decision issue asks for. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Val Alexander <bunsthedev@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a documented hosted pricing tier proposal to the coven-github adapter documentation, and links it from the existing hosted packaging doc so the tier matrix and enforcement mapping live in one place.
Changes:
- Link
HOSTED.mdpackaging guidance to the new pricing proposal document. - Add
docs/pricing.mdwith proposed tier matrix, rationale, and an “enforcement map” tying tier limits to existing adapter mechanisms.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| HOSTED.md | Points readers to the detailed tier matrix + enforcement mapping in docs/pricing.md. |
| docs/pricing.md | New hosted pricing proposal doc: tiers, numbers, and mapping from promises to enforcement knobs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| |---|---|---|---|---| | ||
| | **Price (launch proposal)** | Free (self-host) | **$99/mo** | **$399/mo** | **from $2,000/mo** (annual) | | ||
| | Buyer | OSS maintainers, evaluators, local-first users | A small team with a backlog | Product/platform teams | Security-sensitive orgs | | ||
| | Familiars | Unlimited (you run it) | 1 | Up to 4, per-repo routing | Custom roster | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #17 (a decision issue — this PR delivers the documented proposal; closing the issue is the maintainer's call after the numbers are ratified).
What's proposed
Design principles: flat monthly + daily task caps (no usage billing until cost distribution is known — metering already exists to graduate later); tiers scale on trust-continuity features (familiars/memory/oversight/retention/support), not compute; BYOM everywhere; every promised limit names the shipped mechanism that enforces it — the doc includes a full enforcement map so pricing can never drift ahead of the product.
Explicit non-inclusions: per-seat pricing, overage billing, a free hosted tier (Community is the free tier).
Open decisions flagged for Val: final dollar ratios (1:4:20 proposed), 14-day trial vs. free hosted sandbox (trial proposed), blocking-review-mode placement (policy not pricing, proposed), OSS-org discount (50% proposed).