Public website for trust
The public side of ClastX should explain the product clearly, answer objections, and make plans, downloads, and support feel sharp and understandable.
About ClastX
Build a coding product that feels serious before it feels flashy.
ClastX is being shaped as a coding-first workspace with a public website that handles trust, onboarding, billing, and support without muddying the actual development surface.
Desktop app for execution
The workspace should handle debugging, planning, code review, refactoring, and implementation support where local files and commands actually exist.
Commercial layer around the work
Accounts, billing, usage limits, updates, and support should wrap around the coding product instead of getting tangled inside it.
Design principles
The product gets better when each risky detail has a clear home.
That means putting business rules in the billing layer, real coding access in the desktop app, and visible work tracking inside the workspace instead of hiding it behind generic chat behavior.
- Show the work, not just the answer.
- Keep billing logic explicit and server-backed.
- Protect desktop-only capabilities behind the right surface.
- Make updates, access, and support understandable for normal users.
Current focus