MembershipAll four productsCancel any time

Your subscription funds the team that builds what you ask for.

One membership covers all four products, the community, the request queue, the weekly changelog and the monthly call. Tiers differ in how involved you are. They never change whose requests get built, and no tier moves a request up the queue.


Member

”””[PRICE
” time=”per month”]
  • All four products: LevelUp, Velocity, Publish and Producer
  • The community and the request queue
  • The changelog, every week, with the video
  • The monthly community call, live or recorded

Contributor

”””[PRICE
” time=”per month”]
  • Everything in Member
  • Early access to changes behind flags
  • A seat in the testing cohort
  • Office hours with the stewards

Founding

”””[PRICE
” time=”per year, or once · limited to [n]”]
  • Everything in Contributor
  • Lifetime recognition in the changelog and on the site
  • A named advisory slot on one product
  • First call on new products

Prices are placeholders. Tier contents are final; amounts are not. The Founding tier is limited to the founding cohort of twenty to fifty practitioners.


Enterprise: a change built for your organisation alone

Priced as a project, with its own scope and timeline, and kept visibly separate from the community queue. Enterprise work never jumps the line, and community requests never wait behind it.


Every membership includes

Four products under one rule: AI does the work, a person is at the gate.


Where the money goes

Not tokens. The people and the process that turn your problem into a shipped change.

The stewards
A working practitioner per product who holds its charter, decides every request in public, and is the person who says no.

The AI development team
Intake, analysis, build, verification and the help article, for every accepted request, in days rather than quarters.

Verification and the cohort
Regression, layout, accessibility and data checks on every build, then member testers behind a flag before anyone else sees it.

The community
The queue, the weekly changelog video, the monthly call, and the scorecard that keeps us honest.

The apps run on your own AI keys. You pay your providers directly, and nothing is metered, credited or marked up inside the products. Your subscription pays for the evolution of the product, not for its usage.


Compare the tiers

The last row is deliberate. No tier moves a request up the queue.

What you get Member Contributor Founding
All four products
The community and the request queue
The weekly changelog and video
The monthly community call
A public decision on every request within ten business days
Every changelog entry names you when your problem ships
Early access behind flags
A seat in the testing cohort
Office hours with the stewards
Lifetime recognition in the changelog and on the site
A named advisory slot on one product
First call on new products
Priority for your requests

What you bring: your own AI keys

The subscription pays for evolution, not usage. Each product runs on keys you hold, and none of them meters, credits or marks up inside the app.

Product What it runs on Where the key lives
LevelUp OpenAI, Anthropic Claude or Google Gemini, for every AI feature Shared at the workspace level; never leaves the server
Velocity Anthropic, OpenAI or Gemini, per workspace, with a monthly AI budget that caps spend Per workspace
Publish Anthropic Claude or Google Gemini for writing (DeepSeek, xAI, Moonshot and MiniMax keys also accepted); OpenAI or Gemini for images; Tavily or Serper for live search Pasted in the app, per workspace
Producer Your Claude Pro, Max or Team subscription, through Claude Code Producer never holds an API key

Questions people ask before joining

Yes. Each app runs on keys you paste in: LevelUp and Velocity take OpenAI, Anthropic or Gemini; Publish takes Anthropic or Gemini for writing and OpenAI or Gemini for images; Producer uses your Claude subscription through Claude Code. You pay your providers directly. We add nothing on top and meter nothing inside the apps.
No. Tiers change how involved you are, not whose requests get built. Every request gets a public decision from the product’s steward within ten business days, and every decline comes with a reason. Founding members advise on a product’s charter; they do not move requests. Enterprise builds are a separate, priced path and never enter the community queue.
Membership covers all four. Most members start with one and pick up the others as the changelog shows them what the rest do. If a single-product plan would change your decision, post that as a problem in the queue; it is a fair request.
Yes. Early-access products are part of every membership. The status is shown on the product page, together with the published test report and the list of what has to ship before it is called general release.
A Windows PC and a Claude Pro, Max or Team subscription with Claude Code installed. Transcription, narration and rendering run on your machine. Producer never holds an API key. Version 0.1.0 is not yet code-signed, so Windows SmartScreen warns on first launch.
Twenty to fifty practitioners who already use at least one product, recruited first so the loop runs in public before the community opens to everyone. Founding members are named on the site, hold a named advisory slot on one product, and get first call on new products. The tier is limited and closes when the cohort is full.
Yes. LevelUp, Velocity and Publish all have workspaces with roles for teammates. How team seats are priced is one of the open questions on this page; the answer will be posted here and in the changelog.
[Cancellation and data-export policy, one paragraph, to be written.] The principle is already fixed: your data and your keys are yours, in every product, before and after.
[Trial policy, to be written.] Until then, the queue, the changelog and the charters are public, so you can see how the loop runs before you join.

Start with a problem, not a plan.

Join, post the problem that costs you the most time, and watch what happens within ten business days.