Blink.New

Overview

Blink.new is an AI-powered full-stack app builder: you describe a website, SaaS product, internal tool, or mobile app in plain language, and an agent generates working code, wires backend services, and deploys a live preview. The product markets itself under “vibe coding” and “agentic” building — conversation-first development rather than drag-and-drop no-code.

Maker: Blink (legal entity on the privacy policy: 1Flow, Inc.), a Y Combinator Winter 2022 company founded by Kai Feng, based in the San Francisco Bay Area. Product site: blink.new. The commercial product launched around 2025; the YC company listing remains active with open roles and a small team footprint.

Primary job: turn natural-language prompts into production-oriented apps with database, authentication, hosting, payments (Stripe), file storage, and an AI Gateway for in-app models — without assembling Supabase + Vercel + Clerk yourself. Positioning sits next to Lovable, Bolt, v0, and Replit, with a stronger “zero-config full stack” claim than pure UI generators.

Key features

• Prompt → full-stack app — Chat-driven generation of frontend, schema, auth flows, edge functions, and deployment. Docs emphasize incremental prompts over one giant request.
• Agent mode vs Plan mode — Agent applies code changes; Plan discusses architecture, schemas, and UX without mutating the project. Switching modes is first-class in the product docs.
• Opinionated stack — Web: React + Vite + TypeScript + Tailwind CSS + shadcn/ui + React Router. Mobile: React Native + Expo. Backend: Deno edge functions + Turso (LibSQL/SQLite); optional Supabase for PostgreSQL. Storage: Cloudflare R2. Auth: built-in Blink Auth (email/password, Google, Apple, GitHub, magic links).
• Database without ops — SQL database with visual editor; schema changes described in chat. Turso for edge-native SQLite-compatible storage; Supabase integration when you need Postgres.
• Stripe payments — OAuth-style Stripe connection for one-time charges, subscriptions, portals, and webhooks from natural-language setup prompts.
• AI Gateway (200+ models) — Apps can call text, image, video, and speech models through one OpenAI-compatible interface billed from workspace credits; docs list frontier models and media endpoints.
• Blink Claw (always-on agents) — Product surface for AI “employees” on Slack, Telegram, Discord (and related channels), with dedicated VMs and tool access — separate from the core app builder credit loop.
• Visual editor — Click elements to change copy, color, spacing, or leave agent comments; changes write back into source.
• Preview vs production hosting — Preview URLs on *.sites.blink.new update as you build. Production on *.blinkpowered.com (paid) only updates when you Publish, so live traffic is isolated from experiments.
• Custom domains & SEO tooling — Connect or buy domains (Starter+); docs cover sitemaps, meta, structured data, and AI-search readiness scans.
• Mobile & store publishing — React Native/Expo projects; Max-tier docs cover App Store and Google Play submission paths from inside Blink.
• Chrome extensions — Dedicated build path for browser extensions with popup preview.
• GitHub export / sync — Code ownership claimed as 100% yours; Pro adds two-way GitHub sync and in-app code editing. Export to self-host on Vercel/Netlify/etc. (Blink backend features do not automatically follow you off-platform).
• Version history — Automatic versions after AI tasks with screenshots and restore; useful when an edit loop goes wrong.
• Migrations — One-click-style migration docs for bringing projects from Bolt, Lovable, Replit, Base44, Emergent, Manus, and similar tools.
• Collaboration — Invite Admin/Editor roles; Team plan adds shared credit pools and unlimited free viewers.

Pricing

Blink is freemium with credit-based usage. Exact numbers can shift; figures below are from Blink’s public pricing page and pricing docs as of mid-2026 research. Always recheck blink.new/pricing before budgeting.

Plan	Price (monthly)	Annual-style rate (marketing)	Credits & notes
Free	$0	—	5 daily refresh credits, capped at ~30/month; preview hosting; public projects only
Starter	$25/mo	about $21/mo billed annually	100 plan credits + 5 daily (no monthly cap on daily); production hosting; private projects; custom domains
Pro	$50/mo	about $42/mo billed annually	200 plan credits + 5 daily; in-app code editing; advanced models; GitHub sync; collaborators
Max	from $200/mo	from about $167/mo annually	800–50,000 plan credits + 5 daily; credit rollover (Max); App Store/Play publishing; dedicated support
Team	from about $40/seat/mo	varies	Shared credit pool, roles, unlimited free viewers

How credits work: each AI interaction costs credits by complexity (docs give rough ranges: color tweak ~0.3 cr, contact form ~0.8, auth ~1.5, dashboard ~2.5, full store ~5+). Consumption order: bonus credits → daily refresh → plan credits. Daily credits reset at midnight PT. Starter/Pro plan credits generally reset each cycle without rollover; Max plan credits can roll over. Bonus/purchased/referral credits do not expire.

Production hosting is billed in credits per project by traffic tier (examples from docs: 10K visits/mo → 50 cr/month; 50K → 120; 200K → 240; 1M → 500). Overages keep the app live and charge per extra visits rather than hard-shutting traffic. Changing a production URL slug can cost a one-time credit fee.

Extra credits: buy packs from Settings → Usage (example packs $25/100 cr through $1,000/4,800 cr with 20% bonus at $500+). Auto-reload can top up when balance is low (no 20% bonus on auto-reload). Referral program is roughly “give 10, get 10” when the referred user publishes a first app.

Refunds: official FAQ states subscription fees are non-refundable; cancel anytime and retain access until period end.

Limits & gotchas

• Free projects are public-only — private projects and stable production URLs require Starter or higher.
• Credit opacity — cost varies by model and task size; independent reviews note free daily credits run out quickly during exploratory builds. Claw/agent operations can be expensive relative to simple UI edits.
• Edit-loop regressions — reviewers report the agent sometimes over-edits (for example breaking layouts while moving a button). Version restore is the recovery path; Plan mode before large refactors reduces thrash.
• Complexity ceiling — multi-tenant RBAC, intricate enterprise workflows, and highly custom architectures are where agent output degrades. Serious systems engineering still belongs in Cursor, Claude Code, or a traditional codebase after export.
• Stack lock-in while hosted — Blink masters one stack (React/TS/Turso/Deno). No Vue/Angular/Svelte or Python backends as first-class product paths. External APIs are fine; alternate frameworks are not.
• Self-host caveats — exporting frontend code is supported; keeping Blink-native auth/DB/AI without the hosted platform means re-implementing those services.
• Mobile is real React Native, not magic store approval — say “mobile app” on project create; store submission still involves Apple/Google review process and Max-tier tooling per docs. Third-party writeups note pure web-first bias for many users.
• Hosting is not “all free forever at scale” — SSL/CDN appear on free preview, but production traffic tiers consume plan credits monthly.
• Small-company risk surface — YC listing shows a tiny team; status is monitored via status.blink.new (Better Stack). Evaluate vendor maturity for mission-critical production.
• Support / billing friction — Trustpilot has a small sample with a poor aggregate score for blink.new as of research time; treat third-party review sites as signal, not truth, and verify with a small paid trial.

Community sentiment

Community conversation clusters in r/blinkdotnew, Discord, founder LinkedIn posts, Product Hunt, and comparison threads across vibe-coding subreddits.

Praise (common themes):

• Faster “idea → working MVP” than juggling separate auth/DB/host tools; users who bounced between Lovable, Bolt, and Replit often cite fewer wiring steps on Blink.
• UI quality and instruction-following get positive notes from designers and non-technical founders (structured layouts, spacing, “one-shot MVP” anecdotes).
• Built-in Stripe and auth reduce the “it looks pretty but nothing works” failure mode of earlier AI site generators.

Criticism (common themes):

• Credits feel expensive once you iterate heavily; free tier is a demo, not a daily driver.
• Agent can break working features during small visual changes — same class of issue as other agentic builders.
• Complex architecture and fine-grained control lag developer-first tools (Bolt’s WebContainers IDE, Cursor’s full editor).
• Independent review sites emphasize “great for MVP, not for banking-grade systems.”

Independent reviews describe Blink as closer to directing an agent than dragging components — magical for demos, still needing human judgment for production hardening.

Security & privacy

• Privacy policy (blink.new/privacy, updated May 2026) is published under 1Flow, Inc. Marketing/docs claim encryption in transit and at rest, automatic SSL on apps, and GDPR-oriented compliance language.
• Training on user content: privacy materials state that by default Blink does not use conversations, prompts, or code to train its models or third-party provider models — verify current policy language before enterprise procurement.
• App security tooling: docs cover row-level security patterns, API key handling, and module access policies under Grow → Security.
• Ownership: FAQ claims full commercial rights to generated code with export anytime; free-tier project visibility remains public by policy.
• Payments: Blink subscriptions process through Stripe; app payments for end users also route via Stripe integration.
• Status: operational status published at status.blink.new.

Who should use it

• Founders and indie hackers validating SaaS or marketplace ideas who need auth + DB + Stripe in days, not months.
• Non-technical operators building internal CRMs, dashboards, booking tools, and content sites who will stay inside Blink hosting.
• Agencies and freelancers delivering client MVPs on a shared Team plan, then handing off React code or a live Blink URL.
• Product managers / designers who want interactive prototypes with real data, not static Figma links.
• Builders of AI features who want the AI Gateway instead of managing ten model API keys on day one.

Skip or limit Blink if: you need multi-framework polyglot backends, hard multi-tenant compliance from day one, pixel-perfect long-term design systems under full local IDE control, or offline/on-prem deployment with zero SaaS dependency.

Alternatives

• Lovable — Strong design-forward UI generation and chat iteration; choose when visual polish and Supabase-centric stacks matter more than Blink’s all-in-one edge stack.
• Bolt (bolt.new) — Browser IDE with WebContainers; better when you want a terminal-like developer environment and Node-native iteration.
• v0 — Vercel’s UI-first generator; best for component/landing quality inside a Next.js ecosystem, not full product ops.
• Replit — Cloud IDE plus Agent; stronger when you want a full coding environment and flexible languages.
• Cursor — AI code editor for engineers who own the repo; use after export when you outgrow agent-only editing.
• Bubble — Mature visual no-code for complex business logic without generating React source as the primary artifact.
• Anything (anything.com) and other vibe builders — Competitors in prompt-to-app; compare credit economics and mobile story case by case.

Verdict

Blink.new is a serious contender in the 2025–2026 AI app-builder wave: YC-backed, full-stack by default (Turso/Deno/React, Stripe, auth, hosting), with Plan/Agent workflows and an expanding AI Gateway. It is strongest for founders and makers shipping MVPs and internal tools without assembling infrastructure. It is weakest when you need deep architectural control, predictable low-cost iteration, or regulated multi-tenant systems.

Practical recommendation: start on Free to learn credit burn rates, upgrade to Starter ($25/mo) for private production experiments, and reserve Pro/Max for heavy iteration, GitHub sync, and store publishing. Export early if long-term independence from Blink Cloud matters. Treat marketing “#1 in 2026” claims as ads — evaluate with a real project and the usage dashboard, not the landing page alone.