Wedge page: for teams entering regulated markets - #13
Merged
Conversation
Deploying www with
|
| Latest commit: |
598046d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9efbe716.www-4rw.pages.dev |
| Branch Preview URL: | https://bm-wedge-page.www-4rw.pages.dev |
fosterstack-admin
force-pushed
the
bm/pricing
branch
from
September 12, 2026 16:27
42f0b2c to
0e3d1a9
Compare
Business-model work order §3, in the ordered shape: the situation (one customer, the pile), the mission sentence - the cost of compliance shouldn't determine who gets to compete - what our piece does and does not do (evidence and validated crypto FOR your program; never makes you compliant), the Compliance tier and its nouns, and verify-everything- free-first ending on the test we invite. No claims beyond what the cache does today; the evidence links point at RELEASING, SECURITY (including its not-yet-proven statements) and the requirements matrix. Linked from the Compliance column and the footer; added to the sitemap.
fosterstack-admin
force-pushed
the
bm/wedge-page
branch
from
September 12, 2026 16:27
382d5c0 to
598046d
Compare
fosterstack-admin
added a commit
that referenced
this pull request
Sep 12, 2026
Business-model work order §3, in the ordered shape: the situation (one customer, the pile), the mission sentence - the cost of compliance shouldn't determine who gets to compete - what our piece does and does not do (evidence and validated crypto FOR your program; never makes you compliant), the Compliance tier and its nouns, and verify-everything- free-first ending on the test we invite. No claims beyond what the cache does today; the evidence links point at RELEASING, SECURITY (including its not-yet-proven statements) and the requirements matrix. Linked from the Compliance column and the footer; added to the sitemap. Co-authored-by: FosterStack Admin <317177128+fosterstack-admin@users.noreply.github.com>
fosterstack-admin
added a commit
that referenced
this pull request
Sep 12, 2026
) * Pricing: the Compliance tier lands; four columns, per-product, honest line Business-model work order §2, authority business-model-and-marketing.md §4/§4a. Free drops 'Forever free' and states what free includes (every patch, the -fips image, all release evidence); Team retires 'metrics UI' (the status page is free) and gains SSO (OIDC), per-project analytics and the 1-business-day email target; Business says 'CVE-response target', never SLA; Compliance is $499/month billed annually with the checklist nouns loud and the Sep 5 honesty line: the evidence underneath is public and free, what is paid is the authored analysis, the vendor signature, and the hours. Never 'FedRAMP compliant'/'CMMC compliant'. 'No sales call. No per-seat tax. No enterprise pricing mystery.' under the table; self-serve sentence updated (monthly tiers cancel anytime; Compliance is an annual term); roadmap-honesty lists all the tiers it describes. llms.txt tier list matches. Stacked on the phase3/www-claims branch — both touch the self-serve paragraph. * Roadmap: the Node cache, described as what it is Owner correction (Sep 11, business-model work order): 'an npm remote cache — a third protocol' misled — it read as a package-registry cache or a new wire protocol and it is neither. Replaced with the approved sentence: the same server caching node_modules, test caches, and build outputs by lockfile key, so Jenkins and GitLab jobs stop reinstalling the world on every run. 'Node cache', never 'npm cache', from now on. No timelines. * Roadmap: the dependency cache, final vocabulary (register row 32) The Sep 12 product definition supersedes the Node-cache wording: the feature is the dependency cache - the same server restoring node_modules, ~/.m2, and ~/.gradle/caches by lockfile key, so ephemeral CI agents stop re-downloading the world - npm first. Public vocabulary from now on: 'build cache' (Gradle, Maven) and 'dependency cache' (Gradle, Maven, npm); never 'npm cache', never 'Node cache'. * Pricing: no competitor price, ever (register row 31) The whole $57k parenthetical is deleted, not softened - the owner's hard rule is that no competitor price appears on any customer-visible surface. 'Priced so an engineering manager can expense it without a procurement cycle.' stands on its own. Because this PR's stack rewrites the same paragraph, the older '$57k/year' clause on main is replaced by this text when the stack merges. * Wedge page: for teams entering regulated markets (#13) Business-model work order §3, in the ordered shape: the situation (one customer, the pile), the mission sentence - the cost of compliance shouldn't determine who gets to compete - what our piece does and does not do (evidence and validated crypto FOR your program; never makes you compliant), the Compliance tier and its nouns, and verify-everything- free-first ending on the test we invite. No claims beyond what the cache does today; the evidence links point at RELEASING, SECURITY (including its not-yet-proven statements) and the requirements matrix. Linked from the Compliance column and the footer; added to the sitemap. Co-authored-by: FosterStack Admin <317177128+fosterstack-admin@users.noreply.github.com> --------- Co-authored-by: FosterStack Admin <317177128+fosterstack-admin@users.noreply.github.com>
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
1 participant
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.
Owner cold read — public copy. STACKED on #12 (which is stacked on #10). Merge order: #10 → #12 → this.
Work order §3, content in the ordered shape: the situation → the mission sentence (the cost of compliance shouldn't determine who gets to compete) → what our piece does and does not do (never "makes you compliant") → the Compliance tier and the checklist nouns → verify everything for free first, ending on "if the free evidence doesn't hold up under your audit, the paid tier wouldn't either. That's the test we invite."
Honesty details worth your eye: the verify section deliberately links SECURITY.md "including what it says is not yet proven" and the requirements matrix — the wedge buyer is exactly who will read those cold. No timelines, no banned words (checked), no claims beyond today's cache. Linked from the Compliance cell + footer; in the sitemap.