Create, edit and publish, then run your website and your app from their own dashboard. Every feature shown in real screenshots.
See the features
A Next.js project in React and TypeScript, sent to your GitHub repository. A spec change made in the repository comes back to Eqlo.
See the developer page
Paste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLEqlo is an AI prototyping tool that starts from what your team has already written: a ticket, a spec, a flat mockup or a screenshot of the current screen. It turns that material into pages people can click, fill in and comment on. Once the flow holds up, the code goes to your GitHub repository for the developers.
Paste the text into the request, or attach it as a file. Eqlo reads text files such as txt, md, csv, json and html, up to six files of 15 MB each. From the acceptance criteria, it works out which pages, fields and buttons the flow needs.
Export a frame from Figma or Sketch as an image and attach it. Eqlo reproduces its structure and makes it clickable: fields accept input and buttons lead to the next step. If your request includes exact values, such as a hex color or a font name, they are applied as written.
A capture of the tool your users already know gives Eqlo the layout to start from. You then describe the change you want to test, which makes it easy to compare the current screen with the new idea.
A prototype is meant to be quick. If it takes three weeks, it has turned into a project.
Choose the Prototype project type, which builds clickable screens for testing a flow. Describe the flow or attach your documents, and the pages arrive already linked. No engineering time has been booked at this point.
The two tools do different jobs and work well side by side. Figma is where a team explores and decides how things should look. Eqlo is where that decision becomes a flow people can actually use.
| Figma prototype | Eqlo prototype | |
|---|---|---|
| What you share | frames linked by hotspots | a working site on a private link |
| Form fields | drawn on the frame | typed into, in test mode during preview |
| Data | fixed in the design | stored in tables, importable from CSV or Excel |
| Phone check | a device frame | a 390 × 844 preview and a QR code |
| Feedback | comments inside the file | comments pinned by testers, sent to the AI |
| Output for developers | a spec to read | Next.js code in a GitHub repository |
Many teams keep Figma for visual research and switch to Eqlo when it is time to test. An exported frame makes a good starting point: Eqlo keeps its layout, then wires up the fields and buttons.
Figma remains the better choice for finding a visual identity or for several designers editing one file. Eqlo takes over when you need to see whether people get through the flow.
Testers open a link in their browser or scan the QR code with their phone. They create no account and install nothing, which is often what decides how much feedback you get back.
On screen, they move through the flow and fill in the fields. When something stops them, they click the section and write up to 1,000 characters, signed with their first name. You see the number of open comments and mark each one as resolved once it is handled.
The link stays private. You can renew it, which turns the old one off, or delete it when the test is over. To show two options to two groups, duplicate the project and share one link for each version.
People often use these three words for the same thing, but they describe three different objects. Picking the wrong one can cost weeks.
| Mockup | Prototype | Proof of concept | |
|---|---|---|---|
| What it shows | how it looks | the whole flow | technical feasibility |
| What it leaves out | whether it works | load and security | the finished experience |
| When to use it | to settle a visual | to test with users | to clear a technical doubt |
| Who reads it | the design team | users | developers |
| In Eqlo | an attached image to start from | the Prototype project type | an internal tool on imported data |
The most common mistake is to test a mockup and draw conclusions about real use. Someone looking at an image comments on the visuals. The same person inside a working flow shows you where they get lost.
A feature that has been debated for six weeks can be settled by an afternoon of testing. Engineering time then goes to something five people have actually used, not to a document nobody objected to.
When two people defend two approaches, duplicate the project and build each one. The meeting moves from opinions to what testers did, and it ends with a decision rather than a follow-up item.
Sales asks for a feature on behalf of a customer. You prototype it, show it to that customer and learn what they really need before anyone writes production code. Many requests change shape at that moment.
A prototype can be thrown away, as long as you know what you are throwing away. What usually carries over is the page structure, the layout and the visual choices. Business rules and detailed permissions usually get rewritten by the developers.
The GitHub connection sends the specification and the full Next.js code in React and TypeScript, and edits to the specification made in the repository flow back to Eqlo. A developer opens the project in their usual editor, with nothing to convert before they start.
Sometimes the prototype is enough for internal use. In that case, you publish it as it is and give each colleague a role in the admin, with rights set table by table. Many internal tools start this way and never go through a full development cycle.
Four kinds of teams prototype with Eqlo, each for a different reason.
You judge an interaction by using it rather than imagining it, and you get there without waiting for a sprint slot.
A backlog item becomes something users can try that same week, so the decision rests on what they did.
Clients react to a flow they have handled themselves, which shortens the rounds of back and forth.
You test a technical or commercial idea on real data before asking anyone for a budget.
The developers page and the role pages go further. If the prototype needs to become a product, the SaaS MVP page explains the next stage.
A Figma prototype links frames together: clicking a hotspot shows the next frame. With an AI prototyping tool like Eqlo, you get a working site instead, where fields accept input and data lands in tables. Most teams use both, Figma to design and Eqlo to test.
Yes. Export the frame as an image and attach it to your request. Eqlo reproduces its structure and makes it clickable, and any exact values you write, such as hex colors or font names, are applied as given.
Part of it, yes. The repository contains the full Next.js code in React and TypeScript, so the page structure and layout carry over. Business rules and detailed permissions get rewritten, as with any handover.
They open the review link, enter a first name and pin a comment of up to 1,000 characters on the section concerned. In the studio, you send the comments to the AI one by one or all together.
As soon as the first version exists, the review link is ready to send. A prototype with your colors, your fonts and your real labels usually takes a few rounds of edits in the chat.
Yes, through its values. Write your hex colors, fonts, corner radius and spacing in the request, and Eqlo applies them to the components it generates. The Design tab then lets you fine-tune them without using AI.
Yes. The review link is private and comes with a QR code. You can renew it, which disables the previous one, or delete it at any time.
Yes. You can import a CSV or Excel file of up to 5 MB and 20,000 rows. Testers react very differently to a list of real orders than to a handful of placeholder lines.
You can publish it as it is, on an eqlo.dev address or on your own domain with the Plus plan. You can also send the code to GitHub so your developers take it from there.
Start on the Free plan with five projects and no card. Whoever you send the review link to can comment straight away, with no sign-up.