Kombai

Kombai brings design exploration and frontend development into one workflow, from Figma or an existing codebase through repository code and browser refinement. It is best suited to developers and teams building frontend interfaces; its credit-based plans and desktop or IDE setup make it a less natural fit for occasional or phone-based work.

Overview

Kombai’s infinite canvas supports design exploration, while its code generation works in a real repository and its editable browser gives users a place to refine the result. That end-to-end approach is useful when the job is not finished at the first generated screen: Kombai can also check user flows in a browser, inspect runtime issues, and work through lint or build fixes.

It accepts Figma designs, existing codebases, and websites as inputs. Its native Figma integration can parse complex files, straighten out messy grouping and invisible layers, and extract icons and assets without MCP. Context Graphs provide semantic understanding of a repository, allowing Kombai to reuse components, hooks, tokens, and types. That makes repository context a meaningful advantage over generating each interface as a standalone artifact.

Key features

Kombai applies frontend practices across more than 400 libraries and frameworks. Its stated coverage includes React, Vue, Angular, Svelte, Next.js, Tailwind, shadcn/ui, MUI, and Chakra. The breadth is relevant for teams working across different frontend stacks, though the headline count alone does not establish equal depth for every framework.

Browser checks can exercise user flows and inspect console logs, network activity, performance data, and styles. Kombai can also run lint and build checks, investigate runtime errors, and work through fixes during a task. These checks extend the product beyond code generation, particularly for developers who want a single workflow for generating and refining frontend work.

External services and data sources can connect through MCP servers. Users can run existing Claude Code or Codex subscriptions inside Kombai, or delegate frontend tasks to Kombai through its MCP server from Claude Code, Codex, or Cursor. This interoperability can fit into an agent-based workflow without making Kombai the only tool in it.

The Trust Center lists SOC 2 compliance and controls including encryption at rest, transmission confidentiality, endpoint encryption, and malware protection. Kombai says personal information may be transferred, processed, and stored anywhere in the world, and retained as long as needed for service, legal, dispute, audit, and business purposes. Teams should weigh those data-handling terms against their own requirements.

Pricing

Kombai uses a freemium model. The Free plan costs $0/month and includes one seat, 150 credits at sign-up, and 50 credits daily, up to 300 credits per month. Unused credits roll over up to 150. It is a sensible way to try the workflow, but the monthly credit ceiling limits sustained use.

Pro costs $20/month for one seat and includes 2,000 credits per month, rollover up to five times the monthly allowance, email support, and no AI training on your data. It is the straightforward upgrade for an individual who needs a larger allowance and those stated data and support terms.

Team costs $40/user/month, supports up to 20 seats, and provides 2,000–110,000 shared credits per month. It adds external package indexing, shared rules and commands, unlimited credit rollovers, and centralized billing and management. The per-user price and shared pool make it more relevant to teams that will use those collaboration and administration features than to a solo developer.

Enterprise has custom pricing and custom seats and credit allowances. It includes a custom context engine, dedicated support, SOC 2 compliance, onboarding services, and custom SLAs; it is aimed at organizations that need those tailored services and terms rather than a fixed self-serve allowance.

Platforms

Kombai is available as a desktop app and as an IDE extension, including for VS Code, Cursor, Antigravity, Trae, and Kiro, with installation also through the Open VSX Registry. It supports Linux, macOS, and Windows. There is nothing to install on a phone, so it is designed for desktop-based development rather than mobile use.

Who it's for

Kombai is a strong fit for frontend developers who want design inputs, repository-aware code generation, and browser checks in one workflow. Teams may also benefit from shared credits, rules, package indexing, and billing controls. It is less suited to users who need a phone app, do not work in a desktop or IDE environment, or need a predictable high volume of work from the free allowance.

Pros and cons

• Pros: Context Graphs can reuse repository components, hooks, tokens, and types, grounding generated frontend work in an existing codebase.
• Pros: Figma parsing, asset extraction, browser testing, and lint and build checks cover multiple stages beyond initial code generation.
• Pros: MCP connections and support for Claude Code and Codex subscriptions make it possible to incorporate Kombai into broader agent workflows.
• Cons: The Free plan is capped at 300 credits per month, so frequent use may require a paid plan.
• Cons: Pro is limited to one seat, while Team starts at $40/user/month; shared team features are not a lower-cost multi-seat option.
• Cons: Kombai has no phone installation, limiting it to desktop and IDE workflows.
• Cons: Personal information may be handled or stored anywhere in the world and retained for a range of service and business purposes, which may not suit every organization's policies.

Alternatives

For a different design-to-code option, Figma Make has a free Starter tier with 150 AI credits per day and 500 per month, while its Professional Full seat costs $16 a month and includes 3,000 AI credits per month. Choose it if its Figma-centered plans and web availability suit your workflow better than Kombai's desktop and IDE approach.

Fronty offers a free plan that publishes to a free fronty.live address with Fronty branding, and page and usage allowances vary by plan. Those may suit readers comparing other free options, but their stated details do not establish the same repository and browser-check workflow.

Anima has a free plan with five AI Playground chat messages per day, five Figma imports or website clones, and five Figma-plugin code generations. It may be worth considering when those capped Figma-oriented tasks match the work at hand.

CoderUI offers a free trial, a Pro plan at $29 a month with 500 credits per month, all frameworks, and advanced customization, plus an Enterprise plan at $99 a month with unlimited credits. Quest has a free account with one code download and basically all features. Alloy is another freemium option, and Builder.io offers a free web plan with one included user, up to five users per space, 60 monthly Agent Credits, one published app, and 15 publishes per month. Consider these alternatives when their stated plans or access model better fit your needs. For a broader category comparison, see AI Screenshot-to-Code Tools.

Verdict

Kombai is worth considering for frontend developers and teams who want design exploration, repository-aware code generation, and browser-based refinement with checks in the same tool. Its strongest reason to choose it is that breadth of connected frontend work; the clearest reasons to look elsewhere are the free tier's credit cap, per-seat Team pricing, and lack of phone support.