Build your business. Put AI to work.

Vequro is an AI app builder for real businesses. You describe the app you need in plain English; Lukas, the built-in product strategist, helps you plan it; Vequro builds a working app you can preview, publish and keep improving. No code — and no AI API key to bring.

No. You describe what your business needs in plain English. Lukas turns it into a plan, Vequro builds the app, and changes are made the same way — by describing them.

Lukas is Vequro's built-in product strategist. He helps you think the app through before anything is built — what screens it needs, what data it tracks, how the workflow runs. Brainstorming with Lukas is included on every plan; when you're ready, the final Build Brief costs 1 credit.

You can keep the chat as short as you like, but every build starts from a brief, so Vequro knows what to make. Brainstorming is free; the final Build Brief and Master Prompt cost 1 credit when you're ready to build.

No. Vequro runs on monthly credits included in your plan — there's nothing to sign up for elsewhere and no key to paste in.

No — same answer, plainer: Vequro's AI runs on the credits in your plan. There's no OpenAI account to open and no key to paste in.

Yes. The Free plan is $0, with 50 credits every month and up to 5 apps — enough to plan and build a real first app, not a toy demo.

Yes — Free is $0/month: 50 credits a month, up to 5 apps, and Lukas brainstorming included. Paid plans add more credits and more apps when you outgrow it.

Yes — that's his job. Tell him about your business and he'll suggest the app that removes the most pain first, then shape it into a build brief with you.

No. Vequro builds working apps — screens, records you can add, edit and delete, member sign-ins and real workflows — not just pictures of an app. You preview the real thing before you publish it.

Booking systems, CRMs, client portals, dashboards, intake forms, inventory trackers and internal tools — anything that runs on lists, forms, records and follow-ups. If it runs on spreadsheets today, it's a strong candidate.

Yes. Describe your services, hours and who books what, and Vequro builds the calendar, the booking flow and the client list. Try the cleaning company example in the demo at the top of this page.

Yes. Contacts, pipelines, follow-up tasks and deal stages are core building blocks — describe how your sales process works and Lukas will shape the CRM around it.

Yes. Describe the change in plain English, preview the new version, and republish when it looks right. Small tweaks and big additions work the same way.

No. Edits build on your current app, and every version is saved — changes are small, safe and reversible.

Every time your app is built or changed, that state is kept as a saved version. A bad edit never wipes out the version that worked.

Yes. Because versions are saved as you go, you can restore an earlier state of your app if a change doesn't work out. Restoring brings that version back as your working draft — your live app keeps serving the current version until you publish the restored one, so nothing changes for your visitors until you say so.

Draft is your working copy. Preview is the real app running privately, so you can test it exactly as people will use it. Publish makes a version live at your app's link, for the people you share it with.

Treat Preview as a test drive: click through the flows with sample entries to make sure everything works. Your published app is where real, day-to-day data belongs — don't use preview entries as your records.

Yes. Data in a published app is stored behind the app, not held in the page — reload, close the tab, come back tomorrow, and the same records are there.

Yes. Apps are built around records — customers, bookings, jobs, stock — with adding, editing and deleting as standard behaviour.

No. Vequro provides the storage behind your app. There's no database to set up, host, secure or maintain.

Carefully. Vequro is in controlled early access and we're still finishing the hardening of how published apps protect their data. Start with test or low-sensitivity data, prefer members-only apps, and check the current guidance inside the app before storing sensitive customer details.

Yes — and the PIN is now the extra lock, not the main one. The full per-user protection is live: a published app’s data is served only to people authorized for it, checked on every request, so a visitor without access gets nothing — even with the app’s own page code in hand. You can also set a PIN as a simple front-door code on top of that. For anything sensitive, members-only mode is still the strongest setting: only people you add can open the app at all.

Yes. A published app gets a link you can share with anyone. Public is a choice you make per app — nothing goes public unless you publish it that way.

Yes. Apps can be set to members-only, so only people who sign in to that app can use it and see its data.

Yes. Generated apps can have their own user accounts, separate from your Vequro account — your customers and team sign in to your app, not into Vequro.

Social sign-in options are being rolled out and verified provider by provider. Check the sign-in options shown in your app before promising Google sign-in to your members.

No — don't assume it. Provider sign-ins are enabled only as each one is verified. If Microsoft sign-in matters for your app, confirm it's live for your app first.

Yes. One app can serve your whole team, with a member account for each person.

Apps support member roles and permissions, so you can separate who can view records from who can change them. Set the roles up before you invite the team in.

Yes. When the preview looks right, publish it and share the link. You can republish a new version any time — publishing again doesn't break the link.

No. Your app works on its Vequro link from day one. A custom domain is an optional later upgrade, not a starting requirement.

No. Connecting a domain means DNS changes and security-certificate setup, and the feature is being rolled out carefully — verify it's connected before you rely on it. Your Vequro link keeps working in the meantime.

Once the feature is enabled for your account and your DNS records are set, allow up to 24–48 hours for DNS and certificates to settle. Confirm the domain shows as connected in Vequro before announcing the new address.

You connect a service and grant specific permissions. An app can only use what you've granted, access is requested per integration rather than all-or-nothing, and nothing connects itself.

No. Integrations run under the permissions you granted — if access wasn't granted, the app can't use that integration.

Google connections are rolling out and being verified, so availability can vary by account during early access. Check the integrations list in your workspace, and verify a connection actually works before building a workflow on top of it.

Slack is rolling out in stages. Check your workspace's integrations list for current availability before counting on it for anything important.

Notion is rolling out in stages, like the other integrations. Confirm it appears in your workspace's integrations list — and that the connection works — before building on it.

For more advanced setups, yes — webhooks and external APIs are how apps can talk to other systems. Availability depends on your app's permissions, so test with non-critical data first.

Yes. You can revoke a connection at any time from your workspace, and the app loses access as soon as you do.

No. Connections go through the provider's own secure sign-in — your password stays with the provider, and Vequro holds a revocable access grant, never your password.

Email features are being rolled out and verified. Before you rely on app-sent email — receipts, reminders, confirmations — confirm sending is enabled and tested for your app. During early access, don't let it be the only copy of something important.

Free: 50 credits a month, up to 5 apps. Builder — $29/month or $278/year: 500 credits, up to 25 apps. Pro — $79/month or $758/year: 2,000 credits, up to 100 apps. Lukas brainstorming is included on every plan.

Building work: generating an app, rebuilding it after changes, and finalising a Build Brief + Master Prompt with Lukas (1 credit). Browsing, brainstorming with Lukas, and simply using your published apps don't consume build credits. If you run out, your published apps keep running — you just wait for the monthly refresh or upgrade.

Yes. Credits refresh at the start of each month on every plan, including Free.

Credits are reserved before a build runs, so you're never charged twice for the same job. If a build genuinely fails, check its status in your workspace — and contact support through the app if a failed build looks like it kept credits it shouldn't have.

Yes. Builder is $278/year and Pro is $758/year when billed annually, instead of $29 and $79 monthly.

Yes, from your account settings. Your plan stays active until the end of the period you've paid for, and cancelling doesn't delete your apps or their data.

Two different things — and the answers below separate them. Paying Vequro for your plan is one thing; your customers paying you inside a generated app is another, and that second one is not yet certified. Don't rely on in-app payments for real customer money yet.

No. Your subscription pays Vequro for your plan and credits. Payments inside an app would be your customers paying you — a separate feature, with its own setup and verification.

Not yet — in-app payments are still being verified end to end, so they're not certified for real customer payments today. Verify the current status inside the app before you ever rely on it.

Not certified yet. Don't promise customers PayPal inside a generated app today — check the payments status in your workspace for what is actually live.

Not certified yet — same as PayPal. Until a payment method shows as verified for your app, treat it as unavailable.

They're in early access. The builder is open today; AI Employees roll out to accounts one at a time, as each one is proven in real use — not all at once.

Only within the limits you set. AI Employees work inside approvals and budgets — jobs can be set to wait for your approval before anything changes, and spending caps apply. They're in early access, rolling out as each one is proven.

No — and be suspicious of anyone who promises that. AI Employees are being proven on specific jobs: bookings, follow-ups, keeping records current, billing prep — with approvals and budgets. They help operate the business; they don't replace your judgment, and they are not fully autonomous today.

That's the direction: employees act inside the apps you build and — as integrations are verified — the services you connect, always under the permissions and approvals you've granted. Availability grows as each piece is proven.

Sign in to Vequro and use the support and contact options inside the app — that's the fastest route to a human who can actually see your account. The contact block right below takes you there.