ProductsCruxyBeta
Think, write, search and build. In one workspace.
Cruxy remembers what matters, keeps a vault for each body of work, saves what it makes as artifacts, and searches the web with sources. Add your own MCP tools on Core and up. In your browser, on every plan.
Draft a three-week launch plan for our 28 October launch as a document: goals, then one section per week with owners and the one metric we watch.
This keeps everything to one page. If you need to adjust targets, swap owners, or add a rollback trigger, tell me and I'll update it.
Add a rollback trigger to week 3 and tighten each week to three bullets.
Each week now holds exactly three bullets, and week 3 includes a clear rollback trigger. Let me know if you want the targets shifted or the trigger conditions adjusted.
Cruxy can make mistakes. Check important info.
Launch Plan: 28 October
Decision: We ship on 28 October. No delays, no feature creep. Everything in this plan supports that date.
Goals
- Reach 100 active users within the first three days.
- Keep system uptime above 99.5% during launch week.
- Prove that new users complete the core workflow without support.
Week 1: Lock Core & Stress Test
- Freeze features and push the final release candidate by Monday.
- Run load and failure drills across production infrastructure.
- Owner: Engineering & Product | Metric: Critical bugs (target: 0 by Wednesday)
Week 2: Warm the Funnel
- Send launch teasers and onboard the early access cohort.
- Finalize support playbooks and prepare customer onboarding guides.
- Owner: Growth & Customer Ops | Metric: Waitlist-to-beta conversion (target: 30%)
Week 3: Final Polish & Go Live
- Dry-run launch messages and monitor pre-launch traffic patterns.
- Owner: All hands (Founder leads comms) | Metric: First 48-hour activation rate (target: 40%)
- Rollback trigger: Revert to the previous stable release if uptime drops below 99% or activation falls under 25% in the first 24 hours.
Rebuilt from a live Cruxy account; every control shown is one Cruxy has today. Try it here. Anything that needs an account takes you to sign in.
What you get
One workspace. Every kind of work. Everything here is live today.
How it works
Built around three ideas.
- 01
Conversations do not end
Saved memories and custom instructions come with you into every new chat, so you never start from zero.
- 02
Outputs become artifacts
Documents and code live in a side panel with every version kept, ready to download. Not buried in a chat scroll.
- 03
Cruxy can use your tools
Connect an MCP server and approve its tools once. From then on Cruxy calls them while it answers, and only the ones you approved.
Models
Three sizes. Auto picks. Switch in any conversation.
Fast, Balanced and Deep are stable ids you can depend on. Auto, the default, picks a size for each message by how long and complex it is. Pick one yourself any time.
Compare the modelsWho it is for
Cruxy fits the work you do.
Students
Essays, concepts and problem sets, with an AI that explains rather than just answers. Free covers most of it.
Professionals
Drafting documents, researching markets with web search, working through data, and the routine work in between.
Creators and developers
Scripts, copy and code in the browser, and API keys from the same account for building on the same three model sizes.
Teams
Shared vaults with instructions and memory, owner and admin roles on every plan, and Enterprise for custom limits.
Plans
Free for everyone. Paid plans for higher limits.
Every plan includes Cruxy and Cruxy Code. Prices are in rupees and include GST, with UPI and cards in India.
See all plansEnterprise: everything in Pro, with usage limits and pricing agreed with our team.
Questions
Good to know.
Cruxy can search the web and, on Core and up, call tools on MCP servers you add after you review them. It does not send email, run code, edit your files, or commit to repositories. For your codebase, Cruxy Code works in your terminal.
FREE ON THE WEB
Bring a task. See what comes back.
No card required. The same account signs you in to Cruxy Code and the API.