Flink Join the waitlist
Invitation-only early access · macOS

Built with AI.
Proven in production.

Flink Agent checks the app you built with AI for everything that would break in production, fixes it with your approval, launches it on a server you own, and keeps checking it every night. Your code never touches our cloud.

You're on the list.We'll email you when your invitation is ready.

Invitations go out in small waves. Early members get founding-member benefits.

Flink
The Flink desktop app scanning, fixing, deploying and proving a site called Shop Flink Production deploy@203.0.113.10 ✓ Ready Servers Git Providers Settings Home Sites Deployments Alex Morgan alex@example.com Servers › Production › Shop Scan Shop Read-only. Nothing in your project changes. Review 3 fixes Hard blockers 0 ✕ Critical 1 ! Warnings 2 ? Unknown 1 ✓ Passing 23 23 passing · 3 failing · 1 unknown ✕ Critical Sign-in redirects to a local address SECURITY.AUTH.001 Visitors who sign in on production are sent to localhost and never return ! Warning Missing browser security headers weaken protection WEB.HEADERS.001 Visitors lose transport and content type protections ! Warning Your site stays down after a server reboot SERVER.RESTART.001 Visitors see nothing until someone notices and redeploys ? Unknown Private rows may be readable by strangers SECURITY.RLS.001 Not proven yet. Add two test accounts so Flink can prove who reads what. Unknown never counts as passing. Fix and re-scan Shop on Production · fix 1 of 3 ✓ DoneChoose fixes ✓ DoneFlink agent prepares the fix ◐ RunningReview changes ○ PendingApply as one commit ○ PendingRe-scan Review the proposed changes Reject Approve changes Flink agent proposes a change to 1 file. Approve applies exactly these bytes. src/app/auth/callback/route.ts @@ -9,6 +9,6 @@ export async function GET(req) { const session = await exchangeCode(req) - return redirect('http://localhost:3000/app') + return redirect(new URL('/app', env.SITE_URL)) } ✓ Policy gate: nothing removed Every fix can be undone. Your unsaved work stays untouched. A re-scan runs at once to prove the fix. Deploy Shop Scan & deploy · release r-0412 on Production Steps ✓ Scan23 passing · 0 hard blockers ✓ BuildBuilt on your server · 41s ✓ ShipRelease r-0412 in place ✓ Switch trafficAt one known step ✓ HTTPSCertificate ready ◆ VerifyProven on the live URL LOGS 06:36:55✓manifest: Shop (Node.js) 06:36:55✓build: started on 203.0.113.10 06:37:36✓build: done in 41s 06:37:37✓ship: release r-0412 06:37:39✓switch: traffic on r-0412 06:37:40✓tls: certificate ready 06:37:42✓verify: GET / → 200 in 184 ms 06:37:42◆proven on production 6 of 6 steps · 47s Shop is proven on production https://shop.example.com · verified 06:37 ◆ Deployed Copy address SSL Valid Renews on your server Duration 47s Scan & deploy ◆ Verification Proven on production ✓ Passing ServingDomainRollback targetLast verified r-0412shop.example.comr-0411 ◆Today 06:37 Nightly proof The probe on your server re-checks Shop every night. Your Mac pulls the results. 20 nights ago Tonight 03:00 ✓ 20-night streak · Alerts on: email when production regresses or recovers

The Flink Agent desktop app, drawn from its real screens. Example project “Shop” on an example server.

Your MacYour coding agentYour serverYour live URL, proven

The gap

It works on localhost. That's the easy part.

AI tools write code that runs. Production asks harder questions. Is private data really private? Do your keys stay secret? Does the site come back after a restart? Flink Agent answers them before your users find out.

✕ Hard blocker

Your database is reachable from the internet

Anyone could read or delete your data. This is the kind of problem that turns a launch into an incident.

Launch blocked until it's fixed
✕ Critical

Passwords and keys are saved in your code

Anyone who sees your code can use them.

✕ Critical

Sign-in sends users to your laptop

Users who sign in on your live site end up on a page that doesn't exist.

! Warning

Your site stays down after a restart

Visitors see nothing until someone notices.

? Not proven yet

Private data may be visible to strangers

Flink Agent tests it with real sign-ins and tells you exactly who can see what.

And more, from outdated packages with known flaws to missing HTTPS and a server running out of space. New checks arrive automatically.

How it works

One loop, from your project folder to a proven live site.

No servers to learn and no config files to write. Flink Agent walks you through every step and asks before anything in your code changes.

Connect your server

Bring any server you own.

Add your server's address and sign in once. Flink Agent gets it ready for production while you watch.

  • Your password is used once and never stored
  • Protection, HTTPS and nightly checks, set up for you
  • If a step fails, Flink Agent tells you why and picks up where it left off
Prepare server
Prepare Production root@203.0.113.10 ✓ Host key trusted · SHA256:9f2c…a41e ✓Connect and check the system ✓Create the deploy user and key ✓Harden SSH ✓Configure firewall Install web routing & TLS Install the nightly probe LOG · Install web routing ✓ ssh: identity confirmed ✓ user: deploy created ✓ key: ed25519 installed ✓ sshd: hardened ✓ firewall: 22, 80, 443 ◐ caddy: installing_ Stays on this computer: your keys and server details. Your password is never stored.
Scan

Know what's ready, and what isn't.

Flink Agent reviews your app the way a senior engineer would before a launch. Every check comes back passing, failing or not yet proven, with a plain explanation of what it means for your users.

  • Serious problems block the launch until they are fixed
  • Nothing is marked passing unless Flink Agent proved it
  • Checking never changes your project
Latest scan · Shop
1 critical problem 24 passing · 1 failing · 2 unknown ✕ Critical SECURITY.BUNDLE.001 Client bundles expose server secrets Visitors can recover privileged credentials from public JavaScript. .next/static/chunks/app-3f9c.js contains a service-role key ✓ Passing SECURITY.RLS.001 Private rows stay private A read 3 expected rows; B and anonymous received none. Observation · impact · evidence, for every finding.
Fix

Your AI fixes it. You approve it.

Flink Agent asks the AI coding assistant you already use to fix each problem. Anything unrelated is removed before you see it, and nothing changes until you say yes.

  • You see exactly what will change
  • Every fix can be undone in one step
  • Flink Agent checks again right after, to prove the fix worked
Fix and re-scan · Shop
Review the proposed changes Approve 1 change src/lib/supabase.ts - const key = process.env.NEXT_PUBLIC_SUPABASE_SERVICE_KEY + const key = process.env.SUPABASE_SERVICE_ROLE_KEY export const admin = createClient(url, key) .github/workflows/deploy.yml - run: npm test + run: echo "skip tests" ✕ Removed from this fix This change edits CI configuration, outside the problem being fixed. Include anyway (not recommended)
Deploy

Launched isn't done. Proven is.

Flink Agent launches your app on your server, then visits the live site to confirm it really works. If a new version breaks, it can put the last working one back for you.

  • If a launch fails, Flink Agent explains why and suggests the fix
  • Every version is kept and one click from restore
  • Restoring tells you plainly what changes and what stays
Releases · Shop
Releases Shop on Production · 3 releases r-0412 Serving ◆ Proven on production · today 06:37 Scan & deploy · 23 passing r-0411 ◆ Proven · 2 days ago Roll back r-0410 ! Schema changed since this release ◆ Proven · last week Roll back Rollback: code and config restored; database changes from r-0412 remain.
Keep proving

It re-checks production while you sleep.

Every night Flink Agent re-checks each live site and keeps a streak. Your server never reports to anyone, and your Mac collects the results.

  • Optional email alerts when something breaks, and when it recovers
  • Each alert shows what happened and why
  • One view of every site you run
Production
Production Server · Healthy Total sites3 Active deploys0 Valid SSL3 AlertsOn NameDomainHealthNightly proof Shopshop.example.comHealthy✓ 20 nights Blogblog.example.comHealthy✓ 9 nights APIapi.example.comHealthy✓ Recovered 03:00 ✉ API recovered Verified at 03:00 · open the event

Why Flink Agent

Scanners stop at a report. Deploy tools ship whatever you hand them.

Flink Agent covers the whole path: check, fix, launch, prove it works, and keep proving it.

What you need after it works on localhostSecurity scannerServer panelFlink Agent
Find what breaks in productionReportNoWith evidence
Fix it in your codeNoNoYour agent, your approval
Launch on a server you ownNoManual setupGuided, step by step
Explain what went wrongNoShows the errorExplains it and suggests the fix
Prove the live site worksNoNoOn every launch
Re-check production every nightNoNoWith opt-in alerts

Local-first

Private by design. Your code stays yours.

Flink Agent runs on your Mac. Our cloud knows your account and your plan, and nothing about your app.

Flink Agent's cloud never receives

  • Your code or your project files
  • What Flink Agent finds in your app
  • Secrets, keys and environment variables
  • Your domains or server details

What stays in your hands

  • Your server. Any provider, full control, no lock-in
  • Your AI assistant and your existing subscription
  • Your credentials, in your Mac's keychain
  • Your history. Every problem found, how it was fixed, and the proof
Nothing changes unseenYou approve the exact bytes of every fix.
Every fix is reversibleUndo any change in one step.
Nothing phones homeYour server never reports to anyone.
Honest verdictsUnknown is never reported as passing.

Bring what you built

If it runs on your laptop, Flink Agent can make it production-ready.

Node.jsPHPPythonGoRustRuby Built with Claude Code, Codex, Cursor, Lovable, Bolt, v0 or by hand

Questions

Before you join

Who is Flink Agent for?
Founders, makers and small teams who built a working app with AI and want it live, production-ready and private, without becoming an operations expert first.
Do I need DevOps experience?
No. You need a server from any hosting provider. Flink Agent sets it up, launches your app and explains each step in plain language. When something fails, it tells you why and what to do next.
Which AI coding agents does it work with?
Claude Code and Codex today. Flink Agent finds the one on your Mac and uses your existing subscription. Your AI suggests the fix, and you decide.
Does my code leave my computer?
Only to your own server, when you launch. Flink Agent's cloud never receives your code, what it finds there, your keys, your domains or your server details. It only knows your account and your plan.
What does it run on?
The Flink Agent app runs on macOS today. Your apps run on a server you own, from the provider you choose. Windows and Linux apps are planned.
How does the waitlist work?
We send invitations in small waves so every early member gets a working setup. Early members get founding-member benefits, and each member can invite a few friends. You'll get one email when your invitation is ready.

Early access

Ship the app you already built.

Production-ready, and private by design. Join the waitlist and we'll send your invitation as soon as a seat opens.

Questions or team access: sales@flinkagent.ai

What did you build it with? (optional)

You're on the list.We'll email you when your invitation is ready.

One email when your invitation is ready.