Polymai
Polymai is an AI app-building workflow inside VS Code. It helps you turn a product idea into a planned app contract, hand the work to Codex or Claude Code, preview the result, provision connected services, and track generated apps from your Polymai account.
Polymai is built for builders who want fast app generation without giving up structure, reviewability, or ownership of their provider accounts.
Accounts And API Keys
Polymai uses a bring-your-own-account model. Only a Polymai activation token is needed to activate the extension; other credentials are required only for the providers and features you choose to use.
| Feature |
What you need |
When it is needed |
| Polymai account |
Polymai activation token |
Required to activate the extension and check app quota |
| Cloud AI |
OpenAI API key and/or Anthropic API key |
When you run supported cloud models directly from Polymai |
| Codex or Claude Code handoff |
The corresponding installed and signed-in CLI or VS Code extension |
When you hand implementation work to that coding agent; an API key is not entered in Polymai for the handoff itself |
| Supabase |
Project URL, publishable/anon key, and—when provisioning server-side resources—service-role key, database credentials, and a Management API token |
Only for apps that use Supabase or automated Supabase provisioning |
| Stripe |
Publishable key, secret key, webhook signing secret, and relevant Price IDs |
Only for apps that use Stripe payments |
| GitHub |
Personal access token with access to the target repository or organization |
Only when Polymai creates or publishes to GitHub repositories or GitHub Pages |
| Email |
Resend API key plus a verified sender/domain |
Only for apps that send email through Resend |
| Google Calendar or Meet |
Google Cloud OAuth client credentials |
Only for apps that use Google Calendar or Meet integrations |
Provider secrets are entered after installation and stored through VS Code secret storage where applicable. They are not included in the extension package. Start with test-mode and least-privilege credentials, and never place server-side secrets in generated frontend code. Detailed setup links are included below under Full Setup Checklist and Where To Find Provider Keys.
What Polymai Does
- Turns ideas into app build plans and handoff files.
- Opens build tasks in supported coding agents such as Codex and Claude Code.
- Provides app previews while files are being created or updated.
- Helps provision supported services such as Supabase, Stripe, GitHub Pages, and Resend when configured.
- Tracks app quota and generated app usage through your Polymai account.
- Keeps provider accounts bring-your-own-key, so your OpenAI, Supabase, Stripe, GitHub, and email usage stays under your control.
Install And Activate
- Install the Polymai extension in VS Code.
- Open the Polymai activity bar view.
- Create or open your account at https://polymai.com/account.html.
- Create an activation token on your Polymai account page.
- Paste the activation token into Polymai Settings -> Account in VS Code.
- Connect the provider accounts you want to use in Polymai Settings.
The extension can be installed freely. App quota, subscription status, activation tokens, and app stats are managed through your Polymai account.
Bring Your Own Keys
Polymai does not include provider accounts or provider credits. You connect your own accounts where needed.
Supported configuration areas include:
- OpenAI or compatible AI model providers
- Supabase projects, database access, Auth, Storage, and Edge Functions
- Stripe payments and webhooks
- GitHub publishing
- Resend transactional email
- Local preview and local/offline app data where supported
Secrets are stored through VS Code secret storage where applicable. Generated frontend apps should only receive frontend-safe configuration.
Build Workflow
Polymai works in a staged flow:
- Describe the app or change you want.
- Polymai plans the structure and required files.
- Polymai creates a build task for a coding agent.
- You hand the task to Codex, Claude Code, or another worker.
- Preview and review the result in VS Code.
- Provision connected services when the app requires them.
- Publish or continue iterating.
What You Can Build
Polymai is designed for app projects that benefit from planning, previews, and connected services, such as:
- SaaS prototypes
- dashboards and portals
- internal tools
- landing pages and product sites
- apps using Supabase Auth, database, Storage, or Edge Functions
- apps using Stripe Checkout, subscriptions, or webhooks
- static apps published to GitHub Pages or another static host
See more examples:
https://polymai.com/examples.html
Polymai.com is also built using Polymai.
Requirements
Core requirements:
- VS Code
- A Polymai account and activation token
- Your own provider accounts and keys for the services you enable
Optional external tools:
- Codex or Claude Code for agent-based implementation
- Supabase project access for database, Auth, Storage, and Edge Function provisioning
- Stripe account access for payment features
- GitHub token for repository publishing
- Playwright Chromium for some visual capture flows
- Ollama or another local model service if you choose to use local models
Polymai does not install or operate third-party provider services for you. Provider setup, usage, pricing, limits, and compliance remain under your own provider accounts.
Full Setup Checklist
Polymai can run with only an activation token, but full app-building and provisioning features require connected provider accounts.
For AI planning and app generation:
- Polymai activation token from https://polymai.com/account.html
- OpenAI API key, or another configured model provider
- Codex, Claude Code, or another coding agent if you use agent handoff
For Supabase-backed apps:
- Supabase project URL
- Supabase publishable/anon key
- Supabase service role or secret key for server-side/provisioning work
- Supabase database connection string and database password for schema provisioning
- Supabase Functions base URL for Edge Function calls
- Supabase Management API access where automated Edge Function/Auth/template provisioning is used
For payments:
- Stripe publishable key
- Stripe secret key
- Stripe webhook signing secret
- Stripe Price IDs for fixed plans, or server-side price configuration for dynamic checkout
- Stripe test mode first; live mode only after you have verified your own Stripe setup
For publishing:
- GitHub personal access token with access to the target repository or organization
- Target repository name and branch
- GitHub Pages enabled if you publish static apps there
For email:
- Resend API key
- Verified sending domain or sender address in Resend
- Sender and notification email addresses for generated apps that send email
For optional local/visual features:
- Playwright Chromium installed for screenshot-based visual review
- Ollama running locally if you choose local model execution
You can configure these gradually. Polymai readiness checks show what is connected, missing, or only required for the current app.
Where To Find Provider Keys
Most provider dashboards require you to sign in first. Use test mode keys for early app builds.
Polymai account:
OpenAI:
Anthropic / Claude:
Supabase:
Stripe:
GitHub:
Resend:
Google Calendar / Meet:
Optional local tools:
Privacy And Legal
Use of Polymai is governed by the Polymai legal terms:
https://polymai.com/legal.html
Polymai uses your activation token to check subscription access, quota, and app stats. Provider API keys and secrets should remain in your local VS Code secret storage or your own provider environments.
Support
Website:
https://polymai.com
Account and billing:
https://polymai.com/account.html
Legal:
https://polymai.com/legal.html
Contact:
https://polymai.com/#lead