Choose the $9 Aura landing for your SaaS page
If your immediate job is to launch a SaaS marketing page with capabilities, pricing tiers, and a start CTA, Aura is the $9 choice. It is a single Vite + React long-scroll page built around that job: the page includes a hero, capabilities, intelligence, product showcase, a three-tier pricing section, testimonials, and a start-free CTA. You get the source, one typed content file, CLAUDE.md, and .cursorrules.
Choose SaaS Dashboard at $99 when the thing you need to launch is a working app: its product page describes a Vite and Hono dashboard with Postgres, charts, data tables, user management, and analytics, along with login and auth pages. Those are different purchases. Aura is a marketing page; SaaS Dashboard is the LIVE kit for the wired app. The decision turns on whether this checkout needs to deliver a public product story or application foundations.
Start with the page you need to ship
A page can describe software without implementing the software it describes. Capabilities, tier cards, and a button inviting someone to start are marketing content. They help a visitor understand an offer and decide what to do next. They do not, by themselves, create accounts, persist data, or process payments.
That distinction is the useful pre-checkout test. If the work in front of you is the public-facing page—show the product, explain its capabilities, present the plans, and give a prospective user a next step—Aura matches the shape of the deliverable. If the work includes a functioning dashboard and the app systems behind it, look at SaaS Dashboard instead.
The price difference follows that scope. OTF lists Aura among its $9 landing templates and lists SaaS Dashboard among the $99 LIVE kits. In the pricing ladder, a landing template and a full-stack kit are separate product categories. Comparing them by the number of sections on a sample page misses the implementation each one is meant to provide.
What the $9 Aura purchase gives you
Aura is described as a standalone Vite + React template. Its long-scroll layout moves from a hero through capabilities and an intelligence section to a product showcase. It then presents three pricing tiers, a testimonials grid, and a start-free CTA. For a SaaS team that needs those parts assembled into one marketing page, the template provides a page structure aimed at exactly that presentation.
The content is driven by one typed content file. That matters when the task is to change the page’s message and details: the template page says the sections read from that file, so rebranding does not require JSX edits for the content. CLAUDE.md and .cursorrules are included in the template. These are part of the provided source, not a promise that the page will make product decisions or build your application for you.
The price is for owning the source. Opening the demo is free, but Aura itself is not a free template: its buy line is “Get this template — $9.” The pricing page also categorizes landing templates at $9 each. That is the relevant price if the deliverable is a landing page and the source behind it.
A careful read of the sections also helps avoid treating demonstration copy as company evidence. Aura’s testimonials grid is template copy, not OTF customer testimonials. Its three pricing tiers are the template’s story, not OTF’s prices. They show the sort of page content Aura can present; they do not establish that a buyer has real testimonials or that those example plan prices fit their business. Replace the sample material with your own accurate content before using the page publicly.
11 production screens. Login, database, payments — all wired.
The SaaS Dashboard Kit ships everything already connected. Nothing to set up. Live demo at saas.otf-kit.dev.
What Aura does not wire up
The page you buy with Aura is not an application backend. Aura has no auth, database, or Stripe. A start-free CTA in the page is a section in a marketing template; the existence of that section does not mean sign-up, account creation, storage, or billing is connected. Likewise, pricing cards on the page present an offer but do not turn that offer into a payment flow.
This is a practical boundary, not a knock against the template. Keeping the scope clear lets a team buy the page it needs without assuming that a polished marketing surface also supplies the app behind it. If you already have those application services elsewhere and need the public page, the Aura purchase can fit. If creating the working app is part of the same immediate job, evaluate the kit that lists the app pieces you need.
A useful way to write the requirement is to name the output, not just the product category. “Launch a page explaining our capabilities and plans” points toward Aura. “Launch a dashboard with user accounts and stored application data” points toward SaaS Dashboard. “Put a start button on the page” is not enough information to choose the latter; decide whether the button only communicates a next step or must connect to a working app flow.
When SaaS Dashboard is the right $99 SKU
SaaS Dashboard is the choice when you need the wired app. Its product page identifies it as a Vite and Hono dashboard with Postgres, charts, data tables, user management, and analytics. It also lists login and auth pages, issue tracking, a Kanban board, projects and teams, dashboard cards, a settings panel, inbox and notifications, dark mode, and responsive design. Its stack details include a Hono API and PostgreSQL with schema, migrations, and seed data.
Those are app-oriented contents, unlike Aura’s single marketing page. OTF prices SaaS Dashboard as a $99 LIVE kit on the template page and on the pricing page. If your requirement includes the dashboard and the backend pieces named on that page, follow the SaaS Dashboard kit listing and assess that scope. The higher price corresponds to a different category of source, not a richer version of Aura’s landing page.
Keep the selection grounded in the product page’s description. You can rely on its listed stack and features when deciding whether it fits. Do not infer that every product-specific capability your own service needs is already implemented just because the kit contains app foundations. Compare your requirements with the details shown for the kit, and make the purchase decision against that list.
Make the fork before checkout
Use these questions to decide:
- Is the deliverable a public page with a hero, capabilities, product presentation, pricing tiers, and a start CTA? Aura is the $9 landing template for that shape of work.
- Does the project need the wired app, including the dashboard and backend features described on the SaaS Dashboard page? SaaS Dashboard is the $99 LIVE kit to evaluate.
- Are you reading the displayed pricing or testimonials as evidence about OTF? They are Aura template content, not OTF’s offer or customer proof.
- Does “start” mean a visitor-facing CTA, or does your scope require a functioning application flow? The former is page content; Aura does not include auth, a database, or Stripe.
The pricing page makes the categories explicit: a landing template is $9, while LIVE kits including SaaS Dashboard are $99. That gives the buyer a clean way to map scope to the checkout. Pay for the landing when the job is the landing. Choose the kit when the job needs the wired app described in its listing.
This article is about that pre-checkout choice. After choosing a landing page, the implementation sequence is a separate question; the landing-page build-order guide covers that later step. It does not change which source package is appropriate for the deliverable you need to own now.
FAQ
Is Aura free?
No. Opening the demo is free; owning Aura’s source costs $9. The template page’s buy line says “Get this template — $9.”
Does Aura include working sign-up or payments?
No. Aura has no auth, database, or Stripe. Its start-free CTA and pricing tiers are page sections, not proof that sign-up or payment processing is wired.
Are Aura’s testimonials from OTF customers?
No. The testimonials grid is template copy, not OTF customer testimonials. Replace it with truthful material for the product you are marketing.
Are the three Aura pricing tiers OTF’s prices?
No. They are the template’s story. OTF’s product pricing is on its pricing page: Aura is a $9 landing template, and SaaS Dashboard is a $99 LIVE kit.
When should I choose SaaS Dashboard?
Choose it when you need the wired app and its listed dashboard and backend features. Review the SaaS Dashboard page against your requirements. If the deliverable is just the marketing page, Aura is the relevant landing template.
Sources
- Aura Landing Template: https://otf-kit.dev/templates/aura-landing
- SaaS Dashboard Kit: https://otf-kit.dev/templates/saas-dashboard
- OTF pricing: https://otf-kit.dev/pricing
- Landing page build-order guide: https://otf-kit.dev/blog/how-to-build-a-landing-page-with-ai
- Aura template CTA: https://otf-kit.dev/templates/aura-landing
If your deliverable is the marketing page, get the Aura landing template for $9. If you need the wired app, go to the SaaS Dashboard kit page.
Ship the product, not the setup.
- 11 production screens — auth, billing, team, analytics, settings
- Real database, payments, and login — all wired on day 1
- AI configs pre-tuned so your agent extends instead of regenerates