Early accessYour codebase
Build on the code you already have.
Connect your GitHub repository and describe the change you want. Flinter reads your code, makes the change in the same style, and sends it back to GitHub for you to review.
A drawing of Flinter by our team, with a made-up business. Real screens replace it once early access opens.
What you get
Your code, changed in plain words.
Connect a repository
Pick a repository on GitHub. Flinter reads the code, and the two stay in sync both ways.
Changes in your style
New code follows the patterns already in the project, so it fits with what your team wrote.
Ask in plain words
Ask for a new page, a fix or a new field, the way you’d ask a teammate.
Every change kept
Each change is saved as a version, so you can compare it or go back.
A preview for each change
See the change working on a preview link before it reaches your main branch.
Your team decides
Roles set who can ask for changes, and your team reviews each one in GitHub.
Use cases
What people build with it.
- Web appAPI companyRelay
“A dashboard where our customers sign in, see their usage and pay their invoices”
Customer sign-inUsage chartsInvoices and paymentsSee the page for Relay's kind of business - ToolSupport and managersField orders
“An admin panel for our orders, where support can see everything but only managers can refund”
RolesOrder searchRefunds for managersSee the page for Field orders's kind of business - Web appAccountants, LeedsLedger & Lane
“An app where our clients upload their documents and see the status of their tax return”
Client sign-inFile uploadsStatus per clientSee the page for Ledger & Lane's kind of business
Made-up businesses, drawn by our team to show what Flinter makes. Real Flinter builds replace them once early access opens.
How it works
Describe it.
Flinter builds it.
One sentence in, a live project out, in one conversation.
Questions
Good questions,
straight answers.
What people ask before they join. If yours isn’t here, ask the team.
Still wondering?Ask the team anythingIn your own GitHub repository. Flinter works on it, and it stays yours.
Yes. Code your team pushes to GitHub comes back into Flinter, and changes made in Flinter go to GitHub.
Yes. Every change is a version you can go back to, in Flinter or in your repository’s history.
Flinter is in early access and opens in waves, starting with a small first group. Join the waitlist and we’ll email you the moment your spot opens.
More
More of what Flinter builds.
- Developer toolsBuild from your editor or AI agent.
- DevelopersStart from a working app, not an empty repo.
- Internal toolsDashboards and admin panels on your own data.
Change your app with one sentence.
We’re letting people in a few at a time. Leave your email and we’ll send your invite.
No spam. Unsubscribe any time.