desktop-first orchestration
The desktop AI IDE built to outgrow Cursor and Windsurf.
Acrylic is a premium desktop IDE for builders who want advanced BYOK, visual editing, real terminal control, multi-agent workflows, and local-first AI without renting their entire workspace from a cloud wrapper.
beta launch
A serious desktop system, not another thin LLM skin.
Acrylic combines agent-native chat, visual builder workflows, runtime-aware terminal control, structured planning, and local project context in one desktop environment designed for real codebases.
- Acrylic mode
Shape live interfaces without leaving the IDE.
Insert, morph, inspect, and restructure UI with builder-native operations instead of fighting generated blobs in a chat log.
Visual moves, DOM-aware edits, real layout intent. - Acrylic mode
Use the right model, toolset, and effort level per task.
Acrylic is built around orchestration: planning, tools, model switching, and multi-agent flows that stay understandable.
Plan mode, flow mode, model routing, structured review. - Acrylic mode
Hand work off to a real PTY, not a fake sandbox terminal.
Pass commands to a shared terminal, keep context alive, and decide when the agent acts versus when you take over directly.
Prompt-to-terminal handoff, cancel flow, long-running jobs. - Acrylic mode
Keep every AI edit visible before it lands.
Diff review, hunk-level decisions, pending changes, and runtime context keep Acrylic opinionated where it matters.
Review first, merge second. - Acrylic mode
Your files, repo, and provider keys stay on your own machine.
Identity lives in the cloud for beta access and recovery. Active work stays local, which is how a serious desktop IDE should behave.
Cloud accounts for access. Local machine for the actual work.
More contrast, less fluff, and a product surface that feels alive.
The beta site should feel like the desktop product: layered, opinionated, and a little dangerous. Acrylic is not selling a toy chatbot with a shiny frame.
beta launch
The visual rhythm now leans harder into champagne highlights, emerald depth, and stronger glass contrast without becoming neon sludge.
Layered panels and chrome instead of generic rounded rectangles pretending to be premium.
Depth now comes from motion, not from stacking more empty containers on a dark background.
Accounts in the cloud. Projects and provider keys on your machine.
Acrylic uses accounts for beta access, verified identity, account continuity, device binding, donations, and future billing readiness. It does not need your local files or your BYOK provider secrets in the cloud to unlock the AI tab.
Files stay local. Provider keys stay local. The app is built around your machine being the source of truth for active work.
Verified users get beta access now, while the same account system stays ready for future plans, entitlements, and recovery.
Start with plain language. Ask for code, UI, fixes, architecture, or a builder-driven visual change.
Switch into plan mode when the task deserves structure. The agent can ask questions, split the work, and keep the steps grounded.
Let it read files, create folders, patch code, launch commands, or hand work off to the real terminal when you want full control.
Use diff review, runtime context, and local project intelligence to inspect what changed before you keep going.
Download the Windows beta, sign in, keep your own provider keys, and iterate locally instead of renting your whole IDE from the cloud.
Acrylic is already usable as a real desktop environment, but the product is still in beta. The architecture is growing, the web/auth system is becoming public, and the release process is being hardened in the open.
The first public beta download is Windows-first, with a proper installer and deep-link auth return. macOS and Linux are visible in the roadmap, but not sold as finished today.
Acrylic is free during beta. Donations support development now, while the underlying identity and entitlement system stays ready for paid plans later.
Straight answers before launch.
Bring your own key. Acrylic is designed so your model/provider API keys stay in your local desktop app instead of being centrally managed by us.
Identity, account state, beta access, devices, donations, and future billing readiness. Your local project files and provider secrets stay on your machine.
To manage beta access, verified identities, recovery, device binding, and future monetization without changing the local-first architecture later.
The intent is to outgrow them over time with a more opinionated desktop-native system. Acrylic is still beta, but the product direction is deliberately ambitious.
Public beta, honest legal copy, and a real desktop installer.
The site, auth flow, installer pipeline, and legal templates are designed so you can move from local testing to a real public domain without rewriting the system.