Polymet
Polymet is an AI product designer that turns a plain-English brief, a screenshot or imported Figma frames into pages, components and interactive prototypes, then hands back production-ready React and Tailwind CSS code your developers can ship.
What is Polymet?
Polymet describes itself as an AI product designer: one workflow that starts at a brief and ends at front-end code fit for production. You can open a project by typing what you want in English, pasting a screenshot or sketch, importing frames from Figma through the official plugin, or pulling in an existing codebase from a GitHub repository or a zip. What comes out is reusable components, complete pages for web and mobile, prototypes whose pages are linked into real user journeys, and React with Tailwind CSS underneath all of it.
The workspace has two gears. Canvas holds the whole project in view; Focus mode is where individual screens get refined. Variations let you explore several directions from the same request. Editing works two ways at once: a floating visual panel covers layout, spacing, colours, typography and shadows, while a full code editor with the project file tree sits alongside it. Design systems can be imported, or handed to an Auto option that proposes a theme after a few questions.
The tooling around generation is where Polymet reaches past design. GitHub connections stay in sync in both directions, defaulting to a fresh branch. Supabase-backed Postgres databases, migrations and edge functions can be described in plain language rather than configured. Integrations for payments, email or SMS are detected and wired up, with API keys stored as secrets. Prototypes get persistent preview links that outsiders can open without an account, plus multiple custom domains with automatic HTTPS. Teams invite members, see live presence, comment and chat inside the same project.
The AI layer has grown accordingly: multiple chat threads with project memory, slash commands, clarifying questions before open-ended builds, automatic error correction, version cards with rollback, and a model picker spanning several providers. Since July 2026 an HTTP MCP server lets a coding agent create a project, launch generation and pull the finished code back.
Behind it is Polymet AI, Inc., based in San Francisco and part of Y Combinator's Summer 2024 batch. Its public changelog runs from August 2024 to July 2026. The company's own comparison page concedes that mobile design capabilities trail its web strengths.
What it does
- Generate pages, components and interactive prototypes from a plain-English description
- Export production-ready React and Tailwind CSS code as a zip archive
- Import Figma frames and push finished designs back into Figma
- Keep a GitHub repository in sync both ways as the AI commits and pushes
- Provision a real Postgres database and edge functions described in plain language
- Publish a prototype to one or more custom domains with automatic HTTPS
- Drive Polymet from a coding agent through its HTTP MCP server
When to use Polymet / When not to
A quick filter to help you decide if Polymet is the right fit.
When to use Polymet
- Early-stage startup teams that need shippable screens faster than they can hire a designer, the audience Polymet names for itself
- Design and development agencies handling several client interfaces at once
- Product managers who would rather hand over a clickable prototype than a written PRD
- Front-end and full-stack developers who want React and Tailwind output wired straight into a GitHub repository
- Sales and marketing teams building tailored demos and landing pages without booking design time
When not to use Polymet
- Teams whose priority is native mobile design, since Polymet's own comparison page admits its mobile capabilities trail its web work
- Anyone who needs a stack other than React and Tailwind CSS, as no alternative output is offered
- Buyers who must compare prices before signing up, because no public rate card exists and the pricing page lives inside the app
- Organisations bound to EU data residency, as all customer data sits in US infrastructure with Standard Contractual Clauses as the only transfer mechanism
- Users without a Google account, since sign-in runs exclusively through Google SSO via WorkOS
How to use Polymet
A typical end-to-end flow, from setup to results.
- Sign in with a Google account, as authentication runs through Google SSO via WorkOS
- Start a project by describing the interface you want in English, or upload a sketch or a screenshot
- Bring existing work in if you have it: import up to eight Figma frames through the plugin, or connect a GitHub repository or a zip archive
- Answer the clarifying questions the AI asks on open-ended briefs, or skip them, since they are optional
- Pick or import a design system, or let the Auto option build a theme for you
- Work across Canvas for the whole project and Focus mode for precise edits, generating variations to compare directions
- Refine with the visual editor for layout, colours, typography and shadows, or drop into the code editor
- Link pages into prototypes, and add a database or edge functions by describing what you need
- Invite teammates through Manage Members, share the project, and send stakeholders a preview link that needs no account
- Export the code as a zip and run npm i then npm run dev locally, push to GitHub, or send the design back to Figma
Pros & Cons
Pros
- One continuous path from brief to production front-end code, with no manual handoff between design and development
- Two-way Figma and GitHub workflows, with GitHub syncing onto a fresh branch by default
- Ownership of generated designs and code stays with the customer, who also gets exclusive commercial rights
- The AI training opt-out is explicit, stated on four separate pages, and automatic for Enterprise customers
- Unusually detailed security and legal documentation for a company this young: eleven named subprocessors, encryption specifics and quantified deletion deadlines
- A permanent free plan, so the tool can be evaluated without a purchase
- A dense public changelog, 51 entries between August 2024 and July 2026, showing sustained development
Cons
- No public pricing at all: the rate card sits inside the app and the terms simply invite you to email for figures
- Output is confined to React and Tailwind CSS, with no alternative stack announced
- Mobile design capabilities lag the web ones by the company's own admission, and there is no iOS or Android app
- Sign-in is limited to Google SSO through WorkOS, with no documented email and password route
- Model training on customer content is on by default outside Enterprise, and opting out means sending an email rather than flipping a switch
- Hosting is US-only, with no EU data residency option, no Article 27 representative and no named data protection officer
- SOC 2 Type I was still described as in progress on a security page last updated in April 2025, and the report is reserved for Enterprise customers under NDA
Pricing & Plans
Polymet operates a permanent free plan, referenced in its own terms of service, which allows the tool to be used without payment in exchange for a possible Built with Polymet attribution on public-facing designs. Paid subscriptions exist and are billed in USD through Stripe, combining a subscription with a credit allowance consumed per edited file, but no amount is published: the pricing page is reachable only inside the application after signing in, and the terms direct prospective customers to email info@polymet.ai for detailed pricing. An Enterprise plan is quoted after a scheduled call. No lowest price point can therefore be stated, and no time-limited free trial is mentioned anywhere on the site.
- permanent and free of charge
- with Polymet entitled to add a Built with Polymet attribution to public-facing designs
- billed in USD through Stripe
- combining a subscription with credits consumed per edited file
- amounts are visible only inside the app and no tier names are published
- quoted after a scheduled call
- with AI model training excluded by default
- the SOC 2 Type I report available under NDA and a dedicated contact for legal or security requirements
Data, GDPR & hosting
A consolidated view of how Polymet handles your data.
GDPR overview
Concrete GDPR commitments are published rather than implied. Polymet's Data Processing Addendum, dated 14 May 2026, states it is compliant with the GDPR, the CCPA and similar laws, casts the customer as controller and Polymet AI, Inc. as processor, and names eleven subprocessors with their roles. Transfers out of the EU and UK rely on Standard Contractual Clauses, backed by TLS, AES-256 encryption at rest and least-privilege access. Access, rectification and erasure rights are acknowledged. Breach notification is specific: supervisory authorities within 72 hours, with Article 33 cited explicitly, and affected customers within 24 hours. Two gaps remain: no Article 27 EU representative is designated anywhere on the site, and no data protection officer is named, so data protection enquiries go to a general address.
Who owns the data?
Polymet's terms give ownership of everything you make to you: designs, code and interfaces generated through the service are the sole and exclusive property of their creator, and Polymet states it claims no ownership rights over them. You keep your inputs and receive exclusive commercial rights to your outputs. In exchange, Polymet holds a limited licence to use inputs and outputs to operate the service, maintain quality, fix bugs, improve performance and train its AI models. Under the Data Processing Addendum the customer is the controller and Polymet AI, Inc. the processor. All user content is treated as the customer's confidential information.
Reuse rights
You may reuse whatever Polymet generates for you without asking permission: the terms grant exclusive rights to commercially use, modify and distribute your output, for personal or commercial projects alike, as permitted by your plan. Two limits apply. On the free plan, Polymet may add a visible Built with Polymet attribution to public-facing designs. And because generative models can produce similar results for different people, outputs are not guaranteed unique, although Polymet says it will not knowingly serve identical output to several users. You remain responsible for holding the rights to whatever you submit as input, and for validating and testing generated code before putting it into production.
Data retention & training
Hosting summary
All customer data is processed and stored in US-based infrastructure, according to Polymet's Data Processing Addendum, and no EU residency option is offered. The stack itself is documented: Vercel's global edge network serves the front end and the API endpoints, a Supabase-managed PostgreSQL database provides daily backups, point-in-time recovery, high availability and automatic failover, and AWS, including AWS Bedrock as an LLM provider, appears as hosting infrastructure in the DPA. Storage is deliberately treated as an untrusted environment: data is encrypted with AES-256 either client-side or server-side before it enters storage, and all traffic to the storage backend runs over TLS. Tenant isolation is logical, scoped by organisation and workspace identifiers and enforced by role-based access control at API level. Transfers out of the EU, the UK or other restricted regions rely on Standard Contractual Clauses, together with limited subprocessor usage and least-privilege access. At the time of this review, DNS resolution pointed to an Amazon-hosted anycast address in the United States.
Where Polymet works
Country-level availability.
Not available in
Things to keep in mind
Risks and trade-offs to weigh before adopting Polymet.
- Pricing is invisible before signup, and with a credit model billed per edited file an intensive week of iteration can cost far more than expected; unused credits expire at the end of the subscription term
- Payments are non-refundable as a matter of policy, with exceptions limited to billing errors, duplicate charges or Polymet's own discretion
- Model training on your prompts, designs and generated code is on by default outside Enterprise, and the opt-out requires an email rather than a setting you can toggle
- All data is processed in the United States, so European users depend on Standard Contractual Clauses alone, with no EU representative to address
- Generated code must be reviewed and tested before production: the terms place that responsibility squarely on the user, and output may be incomplete or inaccurate
- A shared preview link is viewable by anyone who holds it, which is easy to forget when circulating client work
- Leaning on generated interfaces can erode a team's own design judgement, since outputs follow learned patterns and accessibility, brand nuance and edge cases still need a human eye
Setup & Integrations
Technical difficulty
Low to get started, higher to finish. There is nothing to install: sign in with a Google account and describe the screen you want, and the FAQ confirms no design skill is needed. Importing Figma frames takes a plugin and a pasted authentication code, while connecting GitHub takes a repository and a branch, with preview rendering in seconds. Databases and edge functions are described in plain language, with no SQL or console. The real technical threshold sits at the exit: reviewing, running and deploying the exported React project needs Node and a developer's habits.
Deployment
Integrations
Supported languages
Behind Polymet
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement Polymet.
Frequently asked questions
What exactly does Polymet produce?
How much does Polymet cost?
Can I start from designs I already have?
Is my content used to train Polymet's AI models?
Where is my data hosted?
Is a DPA available, and are subprocessors disclosed?
How long is my data kept after I ask for deletion?
Do I need to be a designer, and is there a mobile app?
What is the minimum age to use Polymet?
Should you pick Polymet?
Polymet occupies a narrow and useful position: the seam between design and front-end code, which most tools leave to a manual handoff. Where v0 leans developer-first and Uizard leans on templates, comparisons Polymet itself publishes, Polymet holds design generation, component management and shippable React in one workflow, and it has kept adding to that: Figma round-tripping, GitHub sync, Supabase backends, custom domains, an MCP server for coding agents.
Its documentation is unusually solid for a company founded in 2024. The security page, a published DPA naming eleven subprocessors, quantified deletion windows and a training opt-out repeated across four pages suggest a team that expected procurement questions rather than one improvising answers.
Two reservations matter before committing. The first is commercial: nothing about pricing is public. The rate card lives inside the product, billing mixes a subscription with credits consumed per edited file, and the terms invite you to email for figures, so budgeting requires a signup or a conversation. The second is jurisdictional: all customer data sits in US infrastructure, with no EU residency option, no Article 27 representative and no named data protection officer, which will matter to European buyers whatever the Standard Contractual Clauses in place.
Two smaller caveats: mobile capabilities trail the web ones by Polymet's own admission, and the SOC 2 Type I audit is still described as in progress on a page last touched in April 2025, so its current status is unknown.
For a startup team or an agency shipping web interfaces on React and Tailwind, Polymet is worth a trial on the free plan. For anyone with EU data residency requirements or a need to compare costs upfront, the answers have to come from Polymet directly.
- Choosing a selection results in a full page refresh.
- Opens in a new window.