Routing
Web routes live as ordinary files, the kind you would name app/page.tsx. If a path is wrong, you change it the way you always do. Mobile screens are React Native, with tabs, loading states, and error states.
Eqlo for developers, readable React and a repository that is yours
Eqlo writes React, TypeScript, and Tailwind for the web, and React Native for mobile. You sync GitHub in both directions. The npx eqlo CLI does pull, push, migrations, and deploy. Five projects stay free, with one seat and no card. The lockfile lives in the repository, not in a slide.
- 2 to 5 minFirst draft
- npx eqloCLI
- $19Plus, GitHub auto
- 1 seatFree plan
What the generator writes, and what it does not
The generator writes pages, screens, navigation, forms, a visible Postgres schema, and sign-in by email, Google, or Apple. Marketing pages are pre-rendered at build time. Images become WebP. The sitemap and robots.txt are generated. A first draft lands in two to five minutes.
It does not write a proprietary bank payment, a regulated health file, or a claims engine. A very specific trade will need you to take over. Generation can be wrong, which is why each exchange creates a version you can restore, and why a pull request is still a pull request.
Treat the first pass as a proposal. Keep the boring parts: auth screens, the tenant scope, the empty states, the form that posts. Throw the clever layout that fights the design system you already have. Never generate a second source of truth for a table you already run.
The structure of the generated project
The useful test is whether a colleague can clone the repository and run it without a slide deck. Eqlo writes ordinary files. An in-browser code editor sits in the product. Your editor is still the last word. We do not publish a pinned React version on this page. The lockfile in the repository is the source.
Data schema
A Postgres database is created from the description. The schema is visible and editable. Migrations are versioned. Direct read access is there for developers. CSV import and export keep a sheet movable. Secrets are encrypted. Environment variables sit per environment.
Authentication
Email, Google, and Apple, plus password reset and address check. Roles and permissions, organizations for multi-tenant. Reader, editor, administrator. Invitation goes out by email. You do not share a password.
Continuous integration
A branch preview deploys when the project is linked to GitHub. A pull request is a pull request. Automatic GitHub sync sits on Plus at $19 and on Team at $49. Free keeps a manual export.
GitHub sync in both directions
A commit you made at 23:00 is in the project in the morning. A sentence you typed in the chat is on the branch. That is the contract. If export were a paid extra, you should leave.
Branches and pull requests
They stay ordinary Git objects. You review the diff. You reject the screen that was theatre. Eqlo will not be offended. The next sentence in the editor can be do not touch schema, only the empty state copy.
Deployed previews
A preview deploys per branch when GitHub is linked. A stakeholder clicks the thing you have not merged. Hosting on a projet.eqlo.app subdomain is immediate. Your own domain, DNS, and an SSL certificate sit on Plus.
Conflict resolution
Two people editing the same file still produce a conflict. You resolve it the way you always do. The activity log tells you who changed what. We do not invent a magic merge that hides a lost migration.
The CLI, the API, and webhooks
The CLI is npx eqlo. It does pull, push, migrations, and deploy. You run it from a machine you already trust. REST and webhooks are there when another system must hear a payment or a publish. Stripe, Slack, HubSpot, and the other named connectors are asked for in one sentence. Keys are stored encrypted. Errors are handled.
You pick the region at creation: European Union, United States, or United Kingdom. Daily backups, 30-day retention. A full export whenever you ask. Do not put medical data in a first-week build unless you already know the rules.
A realistic week after the first prompt
Day one is the generator: two to five minutes for the first draft, then one to two hours to make a brochure honest. Day two is GitHub: link the repo, open a branch, run npx eqlo pull locally. Day three is the preview URL your stakeholder actually clicks. Day four is the first migration you write by hand because the model guessed a column name. Day five is export or keep sync, your call.
That timeline assumes one seat on Free or three on Plus at $19. Team at $49 adds ten seats when a squad shares one workspace. Backups stay for 30 days in the region you chose at creation. None of that replaces a test suite you trust.
When to stop generating
Stop when the routes, tenant scope, and forms post correctly. Screens that exist only to impress a demo should go before a review, not after.
When to open the documentation
The docs page lists the CLI commands, webhook payloads, and API paths exactly as they run today. Read it before you wire Stripe webhooks into a CI job you cannot unwind on a Friday.
What passes a code review, and what still sticks
Reviewers keep the boring structure: routes, tenant scope, empty states, the sitemap, the form that posts. They throw the theatrical layout. They will rewrite a query that does not match the table they already run. That is still cheaper than discovering the loop was wrong after a quarter.
What still sticks is a very specific trade, a proprietary bank payment, or a regulated health file. Generation can be wrong. A prompt that never mentions acceptance will keep adding screens. The developers who stay are the ones who were allowed to leave with the repository.
Related pages
Prototyping, the SaaS MVP, agencies, and security take over from here.
Frequently asked questions
Is the output a proprietary format?
No. React, TypeScript, and Tailwind on the web, React Native on mobile. You can export and keep going. The lockfile in the repository is the source for versions.
Can I use my own design system?
Yes. Colors, fonts, and radii apply to every screen at once. Generating a second brand is a waste if you already have one.
Will this pass a review?
Often the structure, sometimes the screens. Reviewers will throw away anything theatrical. That is still cheaper than discovering the loop was wrong after a quarter.
Where does the data sit?
In the region you pick at creation. Direct Postgres access is available. We do not sell the rows. Read the residency page before you put personal data in.
Do I need Eqlo after handover?
No. Sync is optional. Many teams keep it for the next loop and turn it off for the parts they now own. That is a normal week.
What does the CLI actually run?
npx eqlo does pull, push, migrations, and deploy. REST and webhooks sit beside it. We do not invent extra commands on this page.
Describe the product. Open the repository before lunch.
Five free projects, one seat, no card. Automatic GitHub sync sits on Plus at $19. The files are yours when you want them.