Runs entirely in your browser — nothing uploaded, nothing installed
Welcome to AMIYO Website Builder
One backend engine, endlessly reconfigured. Pick from – real website types across – categories, and it configures the same battle-tested core — auth, database, roles, search, admin panel — into exactly the shape your product needs. Walk away with a working app or a build-ready JSON spec a developer (or a coding agent) can run with immediately.
–
website types ready to configure
–
product categories covered
–
live, click-to-preview reference apps
1
shared backend core, reused everywhere
The workflow
From idea to working backend in three steps
No accounts, no setup wizard, no waiting on a server. Everything below happens locally in this page.
1
🧭 Pick a website type
Browse by category or search across every type — each one already comes with the roles, entities, and admin sections that make sense for that business.
→2
✏️ Name your project
Give it your brand name and, if you're ready, drop in your Firebase keys. Everything regenerates live as you type — no rebuild step.
→3
📦 Download or preview
Get a working single-file app for types with a live reference build, or a complete JSON blueprint plus README for every other type — ready for a developer or a coding agent to build against.
Why this instead of another template
Built like a real product, not a mockup
Every website type shares the same underlying data model, so switching between them is a config change — not a rewrite.
One backend core, many surfaces
Auth, database, file storage, search, notifications, roles, analytics, and settings are written once and reused by every site type — only the business modules on top change.
Configurable admin panel
A shared admin schema powers every type's back office. Each site simply turns on the sections it needs instead of shipping a bespoke dashboard from scratch.
Live reference apps
Select types ship as fully working single-file apps with demo logins, so you can click through real screens before committing to a build.
Firebase-ready out of the box
Drop in your own project keys and the generated config wires straight into Firestore, Auth, and Storage — or keep the placeholders and fill them in later.
Built for coding agents too
Every download includes a structured JSON spec and README written so a tool like Claude Code can implement the frontend and API against it directly.
Nothing leaves your browser
There's no backend behind this page. Your project name, your Firebase keys, and every generated file stay local until you choose to download them.
Plug in add-on modules, WordPress-style
Toggle optional extras — blog, newsletter signup, live chat, reviews, bookings, SEO pack, and more — onto any website type without touching the core spec, the same way a plugin bolts onto a WordPress install.
What builders say
Illustrative feedback from people prototyping with AMIYO
Example scenarios showing how the same core gets reused across very different products — shown here for illustration, not verified customer accounts.
★★★★★
Went from a blank idea to a clickable food-delivery prototype with vendor and driver logins in one afternoon — the admin panel alone would've taken me a week to hand-build.
JM
Jordan M.
Solo founder, food delivery concept
★★★★★
I handed the downloaded blueprint straight to a coding agent and it built the booking flow without me writing a spec by hand. The entity/roles JSON did the heavy lifting.
RS
Riya S.
Freelance developer
★★★★★
Swapping themes and fonts to match our brand took minutes instead of a design sprint, and the add-on modules meant our newsletter signup didn't need a separate spec at all.
DT
Dana T.
Marketing lead, small agency
Where it fits
AMIYO vs. the usual starting points
Not a replacement for a developer — a much better place to hand one a spec.
| Starting point | Backend shape | Admin panel | Time to first screen | Rebuild cost per pivot |
|---|---|---|---|---|
| Blank codebase | Designed from scratch | Built by hand | Weeks | High — every change is custom |
| Generic UI template | Not included — frontend only | Rarely included | Hours, but no backend | High — backend still unbuilt |
| No-code site builder | Locked to the platform | Fixed, limited sections | Hours | High — migrating off is a rewrite |
| AMIYO blueprint / app | Shared core, reused everywhere | Configurable, included | Minutes | Low — same core, new config |
AMIYO Website Builder
One backend engine, configured dozens of ways. Authentication, database, search, roles, and the admin panel are written once — every website type below only turns on the business modules it actually needs, from a cart-and-checkout flow to a booking calendar to a course dashboard. Nothing here is a separate codebase, nothing calls out to a server, and nothing leaves this HTML file: pick a type, name your project, and download a working app or a build-ready blueprint on the spot.
🧩 – website types
🗂️ – categories
– live reference apps
⚙️ 1 shared backend core
🔐 demo logins on every live app
🧩 12 plug-in add-on modules
/
Theme colour
Secondary accent
Mode
Animation style
Corner style
10px
Density
Button style
Layout width
Background style
Shadow style
Border style
Card style
Image style
Heading style
Hover style
Letter spacing
Spacing scale
Content alignment
Add-on modules (plug in extra sections, WordPress-style)
0 add-ons enabled
Rules are appended to every previewed and downloaded app, right before </head> — nothing is sent anywhere.
Live preview
Every website type below inherits this name, price, and colour automatically.
$9.99
Your Website Name
A quick look at your current styling
Before you dive in
Questions people usually ask first
Both, depending on the type. Types marked with a live badge ship as a complete, working single-file app with demo logins you can click through immediately. Every other type gives you a structured JSON blueprint — the entities, roles, admin sections, and flow — plus a README, so a developer or a coding agent can build the real screens against it.
No. This entire page runs client-side. Your project name and any Firebase keys you enter stay in your browser and are only bundled into a file when you choose to download it.
Pick the closest match — most real products are a combination of a few standard patterns (catalog, booking, roles, admin) rather than something entirely novel. The downloaded blueprint is a starting spec, not a locked template, so custom entities and flows can be layered on top.
Along several independent axes: 16 preset accent colors plus a full custom color picker, 10 font pairings, corner radius, density, button style, card style (solid or frosted glass), image style (vivid, grayscale, or warm), 3 layout widths, 4 background styles, and light/dark mode — plus 12 optional plug-in add-on modules (blog, newsletter, live chat, reviews, bookings, SEO pack, referral & rewards, FAQ & help center, and more) you can toggle on top of any website type — similar in spirit to installing a plugin on a WordPress site, but expressed as a structured spec instead of live PHP.
Yes. Every generated app or blueprint routes its data access through one shared layer, so pointing that layer at Postgres, Mongo, or a custom API is a localized change rather than a rewrite of every screen.
Treat it as a strong starting point, not a finished product. Each category page lists a specific "before you ship" note — like swapping test-mode security rules or wiring a real payment provider — worth handling before real users or real money touch it.
Yes — the theme colour, corner style, spacing density, button style, layout width, and animation style you pick in the brand bar apply live across the whole builder (there's a live preview card in the brand bar itself showing the effect instantly), and the theme colour is recorded in your downloaded config as a set of four CSS variables, so carrying it into the generated app is a direct mapping, not a guess.
Yes — use "Share this build." It encodes your project name, theme, currency, price, animation style, and the open website type into a link. Opening that link restores the same build, so handing a config to a teammate or client takes one tap instead of a written explanation.