Quickstart — business systems
Ship a dashboard, customer portal, API, internal tool, form, website, or automation from a description to a live URL in under five minutes.
Updated
This is the fastest path from "I have an idea" to "it's running on a public URL." Works for any of the nine FlareX system types except Discord bots — for those, jump to the Discord bot quickstart.
The full menu of system types lives on the build page, with templates for each in the template gallery.
A FlareX account (sign in with GitHub, Google, or Discord), about five minutes, and a one-sentence description of what you want to build. No local dev environment.
Sign in
Go to flarex.app and click Get started. Pick GitHub, Google, or Discord — we create your workspace automatically.
Pick a system type (or describe it)
Two paths:
- Start from a category — visit /build, pick the closest system type (dashboard, portal, API, internal tool, form, website, automation), and start from a template in the gallery.
- Start from a description — click Create in the panel and describe what you want in one sentence:
A landing page for my freelance design business with a contact form that emails me when someone fills it out.A dashboard that shows our Stripe MRR, recent signups, and churn risk customers, refreshed every five minutes.FlareX writes the initial code, picks a sensible stack (typically Node + a small framework), and shows you a proposal with a diff. Review and accept.
Add any secrets you need
If your system talks to a 3rd-party service (Stripe, OpenAI, your SMTP, etc.), open Secrets and add the keys. They're encrypted at rest and only decrypted at runtime.
See 3rd-party APIs for the universal pattern.
Deploy
Hit Deploy. FlareX builds your system in a sandboxed container, pushes it to a runner, and streams live logs. First deploy takes 30–60 seconds.
Once it's live, you'll see your public URL:
<system-name>-<6char-hex>.flarex.app.Iterate via chat — AI maintains the system after launch
Don't go back to writing code by hand. Tell FlareX what to change:
"Add a dark mode toggle to the header." "Switch the form from emailing me to writing into the database." "Cache the Stripe call for 30 seconds so we don't hit the rate limit."
Every accepted change is a new version. Roll back from the Deployments tab anytime.
(Optional) Add a custom domain
Pro and Elite plans support custom domains. Open Domains in your system settings, add a CNAME pointing to the platform, and Caddy + Let's Encrypt issue an SSL certificate automatically.
What can I build?
| System type | Example prompt |
|---|---|
| Dashboard | "A live dashboard of our Postgres analytics tables, refreshed every minute." |
| Customer portal | "A portal where customers log in, manage their Stripe subscription, and download files." |
| API / backend | "A REST API with /users and /posts endpoints backed by Postgres." |
| Internal tool | "A lightweight CRM with contacts, deals, and an activity log." |
| Form / data app | "A waitlist signup form with referral tracking and Slack notifications." |
| Website | "A one-page launch site for my SaaS with a hero, features, and pricing table." |
| Automation | "When a Stripe subscription is created, grant the customer a Discord role." |
| Discord bot | "A welcome bot that DMs new members with the rules." (See bot quickstart.) |
What's next
The fastest way to learn the platform is to ship something throwaway first. Pick the simplest version of your idea, start from a template, deploy it, and iterate from there.
- Build a website — static + server-rendered patterns
- Build a dashboard — wiring up the workspace database
- Build an API service — long-lived HTTP services and jobs
- 3rd-party APIs — the universal pattern for talking to Stripe, OpenAI, Google, etc.
- Custom domains — bring your own domain
- Databases — when and how to add Postgres