Pricing
These plans are modeled around the current Zinc stack: Vercel runtime, Clerk auth, Supabase asset storage, Postgres retrieval, Anthropic AI usage, and Recall-powered live meeting capture.
Pricing model
Pricing is built around real infrastructure load: AI generation, live meeting capture, file storage, and shared workspace usage.
Project and document caps exist to protect storage, retrieval, and support costs before teams move into higher-volume plans.
Higher tiers unlock more live meeting capture, more AI-heavy workflows, and larger shared operating surfaces.
Plans
Free
For solo evaluation and light personal workflows.
Included
Basic
For individual operators running client work or internal execution.
Included
Pro
For high-context operators who need continuity across multiple active workstreams.
Included
Teams
For teams that run delivery, approvals, files, meetings, and decisions through Zinc every day.
Included
Cost drivers
Zinc is not just another task board. The stack carries hosting, auth, storage, retrieval, live meeting capture, and multiple AI pathways. The limits below are the current economic guardrails.
Frontend hosting, serverless execution, image delivery, and analytics all scale with active team usage and attachment-heavy workflows.
Auth cost is low at small volume, but shared seats and active workspaces still create a hard floor for every paid account.
Documents, PDFs, screenshots, and uploaded assets compound quickly, so document and attachment caps need to track real storage exposure.
Fast extraction can stay on Haiku, but document assist, project intelligence, and drafting rely on Sonnet-class generation and must be budgeted carefully.
Live bot-based meeting capture is one of the strongest features in the product and one of the clearest usage-cost drivers, so it is intentionally tiered.
Project memory, task history, and document retrieval are cheap at low volume but become meaningful once teams start storing long-lived operating context.
Guardrails
01
Projects are capped on Free and Basic because linked documents, tasks, and meeting history compound storage and retrieval costs quickly.
02
Documents are capped before storage becomes the dominant cost center; higher tiers widen this aggressively because shared work needs archives.
03
AI actions are rate-shaped to keep Sonnet-heavy drafting and analysis predictable instead of subsidizing unlimited generation on low-price tiers.
04
Live meeting bot sessions are separated from ordinary meeting notes because bot-based capture is a real infrastructure cost, not just another UI feature.
Pricing FAQ
01
They are the current recommended launch prices based on the stack in this codebase and the cost profile of AI, auth, hosting, storage, and live meeting capture.
02
Because Zinc is not just storing notes. Each project can accumulate tasks, files, screenshots, retrieval context, and AI usage. The caps are there to keep lower tiers economically clean.
03
Once multiple people are sharing live meeting capture, project memory, and document-heavy workflows across the same workspace, the Teams plan is the safer operational fit.
Early access
If you want the higher-volume plans tuned around your real meeting, document, and AI load, join the waitlist and we can calibrate the model before launch.