Frontend templates: start from an open-source app or a shadcn/ui block

In Apps › Start from a template (or New app › Template), filter by category (dashboards, landing pages, waitlists, auth, CRM, ERP, inventory, education, help desk, HR, chat, docs, e-commerce, kanban, booking, blog, portfolio) or search, open a card to see its details beside the gallery: a large screenshot, its pages, the staff roles it checks, each table with who can read and write it, its router and UI kit, and where its code comes from. Name the app and press Use template; the app opens in the studio. The details have their own link (the address ends in #template=<id>), so you can send someone straight to one.

#What comes in

• Text source files only. node_modules, build output, hidden files (such as .env) and images are left out; put images in a storage bucket. The create result lists what was skipped.
• The template's licence file, kept as LICENSE.md or LICENSE.txt, and a first line in README.md naming the template, its repository and commit, and its licence. Keep both when you share or publish the code.
• Settings record where it came from (repository, commit, licence). A frontend started from a template isn't linked to that repository: to re-sync or open pull requests, import your own repository instead.
• Templates marked Tailwind 3 use the older Tailwind configuration: run npx @tailwindcss/upgrade (or ask Sovariq to upgrade it) before the builder preview shows their styles.

#Templates that set up their own backend

When you choose Use template on one of these, the console opens Set up <template> straight away: it has already checked what the setup would do (a dry run, nothing changed yet), lists each step and any Needs your OK, and one Set up backend runs it. Then First users: give each role the people's email addresses; each account gets a temporary password, shown to you once (copy it or download the CSV), which the person changes at first sign-in. Later opens the app; the same setup stays in the template's details.

Some templates carry their whole backend. Their details show a Backend section; Set up backend runs it in your project, step by step with a tick per step: app roles, the tables with their row-level security (as migrations, each in your migration history with its undo), the access rules, buckets and their rules, document collections and their rules, functions, schedules, live updates and, if you keep the box ticked, sample rows. Every step goes through the same audited tools Sovariq uses (fe_template_backend, run as you, with no model and no credits), and steps already done are skipped, so Try again finishes a setup that stopped. A project that already has some of the template's tables is refused before anything changes: use a new project or a branch, or rename those tables.

• Your existing roles keep their powers: the template's roles have their own names (Campus uses school_admin, not admin), app-admin roles are added to the ones you already let manage users (never replaced), and functions whose source hasn't changed aren't deployed again. If your project already has one of the template's roles and people hold it, the dry run lists what each step would give them ("Role TEACHER already has 2 users; …") under Needs your OK, and nothing changes until you tick the box and choose Set up and give these powers (Sovariq: confirm_existing_roles: true, only after you say yes).
• After the setup, the section lists what is left for you: give yourself the first role (Users › Roles), then switch the schedule on. The template's functions need no secrets: each call gets its project URL and its own short-lived key (Deploying and running functions).
• Sample rows all have ids starting with the template's sample prefix (5a3e1e00- for Campus). Remove sample data deletes exactly those rows; rows people added stay.
• Sovariq does the same with fe_template_backend (it can do a dry run first with dry_run: true) and removes sample rows with fe_template_sample_data.
• Campus (school management): 22 roles, each with its own portal (leadership, back office, teaching, the clinic, front desk, transport, hostel, fee and exam offices, counselling, students, families, applicants); 118 tables with row-level security where families see only their own children, teachers only their classes, health records only the nurse and the school's leaders, counselling notes only the counsellor, and salaries only the person, the accountant, HR and the director; guardians record consent per child and download or ask to erase their child's data (erasure also removes the family threads, the student's profile and sign-in account); the AI assistant reads a child's data on the server only, with the guardian's consent, and every AI feature is only for the roles it lists; rollback SQL for every migration; the quiz_questions and homework collections; nine functions (fee reminders, report cards, push notifications, Razorpay payments, group chat keys, the AI assistant, bulk import and export, private file links and retention, which deletes old records only once the school switches automatic deletion on in Settings › Privacy). Every schedule ships switched off, and the newsletter sign-up stays hidden until the school opens it (the office sends the confirmation links). The starter pins @sovaria/sdk 0.12.0.
• Campus needs a paid plan: the app has about 281 files and Free holds 200 per frontend, so on Free both Use template and Set up backend say so. Campus is for new projects only: a project set up with its earlier version (2026-11-08, 38 tables) is refused with that reason. Set the new version up in a new project or a branch.

#With Sovariq

Ask Sovariq for "a CRM to start from" or "a login page like shadcn's": it lists matching templates (fe_list_templates), and after you confirm creates the frontend from one (fe_use_template), then adapts it to your tables.

Templates are chosen by hand and pinned, so an update upstream never changes your app. Every entry was checked for a permissive licence file at its commit; templates that need TanStack Router, Next.js or a monorepo, or that have no licence, are left out.