Many minds, one refined result.
WaxFrame puts multiple AI assistants to work on your document. Start from scratch and we'll generate a draft — or bring an existing document to refine. Either way, the Builder writes and revises while the Reviewers give specific, numbered suggestions. Round by round it improves; you're done when all your reviewers agree the document is at its best. Your free trial includes 3 rounds on purpose — the Chocolate Chip Cookies template (Menu → 📋 Template - Use) converged by round 3 in every one of 11 test runs while we were sizing the trial, so you can see the whole cycle start to finish before spending a dime.
Pay-as-you-go through each AI provider — no subscription, no minimum. Most users top up once a quarter, not once a week. See the full pricing breakdown
Your hive is a team of AIs. Every AI reviews your document each round; one is the Builder — the AI that rewrites it.
Minimum 2 AIs. 3+ recommended so the hive can break its own ties on conflicting suggestions.
Click any AI below to add its key, pick its model, and (when ready) crown it Builder. New here? Tap the ⓘ above for cost, keys, and the full setup guide.
This is the most important page in the whole setup. This section defines what your project is all about. Every AI sees this information on every round — it's their entire understanding of what you're trying to build. The more specific you are the better your project will be (garbage in, garbage out). A few extra minutes here pays off in every round that follows.
New to WaxFrame? Click 📋 Use Template above and hit the gold Quick Start button at the top of the gallery — one click applies a low-stakes Chocolate Chip Cookies demo so you can see the whole hive flow before bringing your own document.
Fields marked * are required to continue.
What kind of document is this? Be specific — cover letter not document. This is the first thing every AI reads and it sets the format, length, and tone for the whole session. If there is one thing the AIs should never forget, put it here.
Who will read this? The AIs use this to calibrate tone, vocabulary, and how much to explain. IT Director and VP of Facilities gives very different results than general public. The more specific you are, the more consistent every round will be.
What do you want to happen after someone reads this? Approve the budget, schedule an interview, understand the three options and pick one. This is the finish line the AIs are working toward. Vague here means vague everywhere — this field has more impact on quality than any other.
Draw the fence. AIs expand into adjacent topics unless you explicitly stop them. Cover both sides — what must be included and what must not be included. Example: wireless networking only — no switching, routing, or security products.
How should it sound? A few adjectives — professional, confident — is a floor that works but leaves a lot open to interpretation. Richer is better: Direct and confident, not stiff — like a peer they'd want to work with. Say what to sound like, what to avoid, and who's reading. Bland inputs produce inconsistent outputs across rounds.
Hard rules that must survive every round — things the AIs should always or never do. Example: do not add new sections, always use Oxford commas, never change the numbers in the cost table. You can also use the Notes drawer on the Work screen for one-round-only instructions.
Pick a mode that matches what your document needs. The Builder is told the rule for the mode you choose, and round-end and convergence-time guards fire accordingly.
Optional. Source material The Hive will reference on every round but never edit — job descriptions (rules and responsibilities), RFP requirements, style guides, scoring rubrics, prior decisions, vendor claims. Distinct from Notes (round-to-round directives) and from your Starting Document (the document under construction). When you add more than one, order matters — the first document reads as most authoritative to the hive; use the ▲ ▼ arrows on each card to reorder.
Three buttons below let you choose where your starting document comes from. Click Upload File to upload a Word doc, PDF, or other file you already have. Click Paste Text to paste text directly. Click Start from Scratch if you want the hive to generate a first draft using only your project goal.
Click the area below to browse for a file, or drag and drop one directly onto it.
Your preferences are saved in this browser and apply to every project on this machine. Changes save automatically.
Manage the WaxFrame Pro license saved in this browser. Your key stays local; WaxFrame only contacts Gumroad when you submit or replace it.
How the hive behaves during hands-off Auto runs. These only take effect while Auto is on.
WaxFrame slows itself down on purpose so the hive can't get rate-limited when multiple AIs share one provider — that's the default and it's fine for almost everyone. You probably don't need to touch anything here. Only lift a cap if you pay for a higher tier on one of these providers AND you have two or more AIs running through it (e.g. two Cohere variants in your custom AIs, or a server import with multiple models on one endpoint). Each row has a "Check your limits" link to that provider's usage page so you can see what your tier actually allows. Leave a row empty to use the default. Changes take effect on your next round.
Which AI reads text out of scanned or garbled PDFs — used by the "Re-extract with AI Vision" button and the automatic pass on image-only pages. It uses that provider's configured model.
Mirror toggles for the work-screen footer pills, plus background refresh of provider model lists.
Save a checkpoint to a folder on your disk automatically as you work — so if your browser cache gets cleared, the tab crashes, or you switch machines, you have a fresh recovery point ready. Pick a folder once and forget about it. Manual Save Checkpoint on the Checkpoint screen still works for one-off saves anytime. Requires Chrome, Edge, or Opera (file-system API not exposed in Firefox/Safari).
~/Documents — pick or create a WaxFrame subfolder there. The choice is remembered across sessions (one permission prompt at session start).
Off by default. Turn these on only when troubleshooting a specific issue — they have a small memory + speed cost while active. Power-users only; nothing here is needed for normal use.
WaxFrame stores everything locally in your browser across three storage layers — nothing leaves your machine. Each button below targets one layer; the last wipes everything. Wipes are irreversible from inside the app; save a checkpoint of anything worth keeping first (Menu → 💾 Checkpoint - Save), or use your existing export buttons on the work screen. Each wipe needs a two-click confirm. After a wipe the page reloads so the app starts fresh.
A checkpoint is a single JSON file that captures whichever pieces of your WaxFrame state you choose — project setup, reference material, starting document, in-progress session, hive composition, model picks, API keys, Builder selection, license. Save one before a risky round, before clearing a project, or as a periodic safety net. Restore one to bring those pieces back — pick which sections to apply; the rest of your local state stays untouched.
Pick which sections of your current local state go in the checkpoint file. Each row describes what’s in that section and shows what’s in your live state right now. Tick the sections you want included; untick what to leave out. License is included by default for self-portability (work → home on the same machine) — untick it when sharing the checkpoint with anyone else.
Only restore checkpoints you created or trust. A checkpoint file can replace your project, AI setup, API keys, license key, and session state. After picking the file you’ll see a side-by-side comparison — tick only the sections you want to bring in. Unticked sections keep their current local values byte-for-byte.