Free local
+Desktop workbench on your machine.
+Local engine and MCP flows.
+Prompt -> validate -> preview -> patch.
+Use it against your own codebase.
Pricing
Download first. Pay when the workflow proves itself.
Start local. Run Userface on a real SaaS screen. If the loop saves your team from another AI cleanup sprint, then pricing can become interesting.
Pro
+Hosted AI routing.
+Usage analytics.
+Saved workflows.
+Sharper team ergonomics.
Team
+Governance that matches real teams.
+Shared contracts.
+Design-system collaboration.
+Onboarding for real UI teams.
The only plan that matters is the one that controls generated UI.
Free local proves the core loop. Pro and Team add the productized layer around hosted routing, analytics, shared contracts, and governance.
Pricing questions.
Why not a full pricing grid?
Because the honest move is to try the workbench first. Pricing should follow real usage, not theater.
What can I do today?
Download the desktop app and put it against a real screen your team already needs.
When should a team contact you?
When you want Userface connected to an existing design system, governance workflow, or production UI backlog.
Make the product earn the pricing page.
Bring a billing dashboard, settings screen, CRUD table, or component state workflow. Let the workbench prove it belongs.