Aura (aura.build) — AI landing page builder with HTML export

• Aura

  This page

  PricingRival leads

  • Free to browse and remix, but generation needs a trial or credits
  • Paid plans tier by monthly prompt allowance
  • One-time credit packs that never expire

• Lovable

  PricingRival leads

  • Free plan with a small starting credit grant
  • Paid plans meter usage by credits
  • Team tiers add seats and shared billing

• Framer

  PricingRival leads

  • Free plan for one site with limited bandwidth and AI credits
  • Paid site plans scale by credits, bandwidth, and CMS
  • Enterprise tier above that

1. Aura — official site
2. Aura — plans, prompt allowances, and credit packs
3. Aura — its own comparison against other AI builders
4. Aura — privacy policy (DesignCode IO Pte. Ltd.)
5. Lovable — plans and credits
6. Framer — site plans and credits

Free tier

Yes

Pricing summary

Aura is freemium, but the free tier is narrower than the word suggests: you can browse, remix templates, export HTML, and read the DESIGN.md files behind free templates, yet every AI prompt needs a trial or credits, each project is capped at a couple of pages, the CMS is limited, and output is licensed for personal use only. The paid tiers are Pro, Max, Ultra, and Elite — they climb by monthly prompt allowance rather than by features, and all of them unlock the things people actually buy Aura for: full commercial use, Figma export alongside HTML export, a proper CMS, custom domains, and the pro template and component libraries. Every paid tier opens with a short trial that includes a handful of prompts, but it asks for a payment method up front, so cancel before it ends. If your usage is lumpy, there are one-time credit packs that never expire and draw down automatically once your monthly allowance runs out — though credits only buy generation capacity and will not unlock the paid features on their own. Annual billing is discounted well below monthly, and unused monthly prompts do not roll over.

Reviewed on 19 September 2026 · Aura — official pricing

• A pro template is the starting point

  Instead of dropping you into an empty prompt box, Aura expects you to begin from a curated template that already has spacing, hierarchy, and type worth keeping. The first generation inherits that taste rather than inventing it from scratch.

• Real code, not a proprietary format

  Everything Aura produces is standard HTML, Tailwind CSS, and vanilla JavaScript. There is no framework runtime to adopt and no export that only half-works — the pitch is explicitly that there is no vendor lock-in.

• Full-site export and Figma round-trip

  You can export the whole site as HTML files to host wherever you like, and on paid plans you can also move the design into Figma. Import works in both directions, so an existing Figma file or a live URL can seed a project.

• @ references for real design context

  Prompting supports @ mentions for templates, components, snippets, and earlier iterations. Aura documents this as adding up to a large block of context — roughly a couple of thousand lines of code — which is how you steer a generation precisely instead of hoping.

• Advanced Design Mode for the last mile

  After a generation you can adjust layers, spacing, measurements, component swaps, colours, and responsive breakpoints visually, rather than re-prompting and losing whatever else changed.

• Predictable generation accounting

  Aura charges one prompt as one credit across whichever model you choose, instead of metering tokens, attachments, and history separately. That makes a design-iteration budget something you can actually estimate.

• Multi-page sites, CMS, and publishing

  It is not limited to a single page: you can build linked multi-page sites with page transitions, drive them from a CMS, publish to shareable subdomains, and attach a custom domain without leaving the tool.

• Built for handoff, not just for building

  SEO settings, an MCP server for driving Aura from an external agent, a design-system format in DESIGN.md, and a template marketplace all point at the same idea — the output is meant to move into a real workflow rather than stay in the builder.

1. 1

   Start from a template, not a blank page

   Pick a pro template that already matches the kind of page you need. This is the step that separates Aura from prompt-only builders — the layout quality is decided before generation begins.

2. 2

   Prompt with references attached

   Write the prompt and pull in the pieces you want with @ mentions — a hero block, a pricing grid, a testimonial section, an animation snippet. You can also import an existing site URL or a Figma file to give the model something concrete to follow.

3. 3

   Refine visually, not by re-rolling

   Switch into Design Mode to fix spacing, swap components, adjust breakpoints, and set colours. Because you are editing rather than re-prompting, the parts you already liked survive the change.

4. 4

   Wire up content and pages

   Add the remaining pages, connect them with navigation and transitions, and load copy through the CMS once the layout is settled.

5. 5

   Publish one way, export the other

   Either publish to an Aura subdomain or a custom domain, or export the site as HTML and Tailwind to host anywhere. Teams with a design review step export to Figma first and ship from there.

• Designers who ship landing pages

  You get to make the visual calls — template, type, spacing, motion — and hand over something a developer can read, instead of a mockup that has to be rebuilt.

• Design engineers and frontend developers

  The output is HTML, Tailwind, and vanilla JavaScript, so the starting point arrives in the same language as the rest of the codebase rather than as an opaque component tree.

• Founders and product managers launching

  When the launch page is the deliverable and there is no design team to route it through, template-plus-prompt gets a credible page up without pretending the person is a designer.

• Agencies and template sellers

  Repeat landing pages and a marketplace for selling templates suit people producing the same kind of page for different clients, provided the paid tier covers commercial use.

Where the work happens

Aura is a cloud service, not a local tool: you sign in, prompts are answered server-side, projects live in your account, and sites are published from Aura’s infrastructure. Nothing about the workflow is offline.

What the output actually is

Standard HTML with Tailwind CSS and vanilla JavaScript, exportable as a complete site. This is the product’s central claim and the reason it can be hosted on any provider or continued in any code editor.

Model access

Generation runs on third-party frontier models rather than a single in-house one, chosen from a picker inside the prompt bar. The same credit is charged regardless of which model you select, which is what makes the one-prompt-one-credit rule hold.

The free tier cannot generate

Worth stating plainly because it is unusual: on the free plan AI prompts are disabled entirely. You can browse, remix, and export, but producing a new page requires a trial or purchased credits, and free-plan output is personal use only.

Commercial rights are a paid feature

Commercial use, Figma export, custom domains, and the pro template libraries sit behind a subscription. Credit packs buy generation only and explicitly do not unlock those features.

Publisher and payments

Aura is operated by DesignCode IO Pte. Ltd., the company behind the Design+Code learning brand, and subscriptions are billed through Stripe with major cards and Apple Pay. Support runs through the same organisation.

Data handling

The privacy policy covers account details, usage and device data, and payment information, and allows sharing with service providers and business partners. It sets out access, correction, deletion, and portability rights, with retention limited to what the stated purposes need.

Buying it

Paid tiers start with a trial that includes a small number of prompts but requires a payment method, so the trial is not a free ride — cancel before it ends. Annual billing is discounted against monthly, and monthly prompt allowances reset rather than accumulating.