Write the boilerplate.Ship the product.
Real React and TypeScript in your own GitHub repository. Every prompt is a commit, every file is yours — Firelent just writes it faster.
TypeScript
React
Vite
Tailwind CSS
GitHub
Git
Vercel
PostgreSQL
Node.jsTypeScriptReactViteTailwind CSSGitHubGitVercelPostgreSQLNode.js01// real code
Code you'd actually merge.
React, TypeScript, Tailwind and Vite — typed components, clean routes and readable data files. No proprietary runtime, no generated soup.
02// git-native
Every prompt is a commit.
Link a project and Firelent pushes every build to a private repository in your own GitHub account — with the prompt as the commit message. Your history reads like a changelog.
03// bring your repo
Start from what you already have.
Import an existing project from GitHub or as an upload, and change it by chat. Firelent reads the codebase on demand instead of guessing.
you/storefront
React · Vite
04// surgical edits
Small change, small diff.
Edits touch the lines that matter — not the whole file. Every change is checked before it's saved, and every version can be restored.
@@ -14,3 +14,3 @@ export function Pricing()
1 file changed, 1 insertion(+), 1 deletion(−)
05// backend included
Data and auth without the plumbing.
Firelent Cloud gives every project collections, queries and user accounts through a tiny typed SDK. Export everything as SQL whenever you want.
await db
.collection("orders")
.add({
item: "Espresso",
qty: 2
});
orders
06// precise context
Point at the line. Say what to change.
Open the code view, reference any file or line, and ask. Firelent changes exactly that — no hunting through a wall of output.
07// ship it
From commit to your domain.
Publish with SSL on your own domain in a click — or deploy an imported project straight to your own Vercel account.
FAQ
Frequently askedquestions
What developers ask before they let Firelent near a codebase.
Websites are React and TypeScript on TanStack Start and Router, built with Vite and styled with Tailwind CSS, with shadcn/ui components. iPhone apps are React Native.
It’s the stack you’d pick yourself — no proprietary runtime underneath.
Yes. Link a project to GitHub and every build lands in a private repository in your own account, with your prompt as the commit message. You can also browse and download files right in Firelent.
The code view in Firelent is for reading, searching and referencing — changes happen by chat. To work by hand, use your repository.
Firelent pushes to the repository on every build and doesn’t pull changes back yet, so keep hand-written work on its own branch.
Yes. Import it from GitHub or upload it, then change it by chat. Firelent searches and reads the files it needs instead of loading the whole codebase.
Firelent Cloud: collections with filters and sorting, safe counters, unique fields and email accounts with password or one-time codes — through a small typed SDK. Export everything as PostgreSQL whenever you like.
Custom server code, webhooks and scheduled jobs aren’t available yet.
Small requests become targeted changes to the files that matter, not full rewrites. Every change is checked before it’s saved — syntax and imports — and every version is kept, so you can go back for free.
Publish on Firelent hosting with your own domain and SSL. Imported projects can also deploy to your own Vercel account. And since the code is yours, you can take the repository anywhere.
Not yet. Today you work in the studio, in the iPhone app or through Telegram.