Build a website

You don't need a static-site generator, a hosting provider, and a separate domain to ship a website. Describe what you want and FlareX builds it.

What FlareX picks for you

For a website prompt, the default stack is a small Node server (typically Fastify) serving server-rendered HTML, with Tailwind for styling. No frontend build pipeline you need to think about; everything ships in one container.

If your prompt asks for client-side interactivity ("a slider that…", "a live counter that…"), FlareX layers in a small amount of JS — usually plain TS that hydrates a few elements, not a full SPA. You can ask for Next.js or React explicitly if you want a richer client.

Prompts that work well

Lead with what the page is for, then what's on it, then what should happen when someone interacts.

Examples:

A one-page marketing site for my freelance video editing service.
Hero with my name and "Video editor for tech YouTubers". Three sample
clip thumbnails (use placeholders), a contact form, and my email in the footer.

A 4-page docs site for my open-source library. Pages: intro, install,
API reference, examples. Sidebar nav. Code blocks with syntax highlighting.

Adding a contact form

If you ask for a contact form, FlareX wires it up to send you an email (using SMTP via secrets) or store submissions in the workspace database.

1. 1

   Decide where submissions go

   Tell FlareX one of:

   • "Email me at [email protected] when someone submits."
   • "Store submissions in a contact_submissions table I can read later."
   • "Post submissions to my Slack via webhook."
2. 2

   Add the credentials

   For email, add SMTP_URL to Secrets (e.g., smtps://user:[email protected]:465). For Slack, add SLACK_WEBHOOK_URL.

   See the 3rd-party APIs overview for the universal Secrets pattern.

3. 3

   Test it

   Open your live URL, submit the form, and check the destination. If something doesn't arrive, tail logs from Deployments → Logs to see the request and any error.

Custom domain

By default your site is at <app-name>-<6char-hex>.flarex.app. To use your own domain (Pro and Enterprise):

1. 1

   Open Domains in your app

   Settings → Domains → Add domain. Enter your apex or subdomain.

2. 2

   Add the CNAME at your DNS provider

   Point a CNAME at the target FlareX shows you. Save.

3. 3

   Wait for the cert

   Caddy issues a Let's Encrypt certificate the first time someone hits the domain. Usually within a minute. The status badge in Domains turns green when ready.

Iterating

Don't reach for an editor when you want to change a page. Describe the change:

"Make the hero headline shorter and bump the font size." "Swap the third feature card for a testimonial." "Add a 'How it works' section between the hero and pricing." "Make the form tell people to expect a reply within 24 hours."

Every accepted change creates a new version. Roll back from Deployments anytime.

What's next

• 3rd-party APIs — wire in Stripe, analytics, your CMS
• Webhooks — receive form submissions from external sources
• Custom domains — full BYO-domain flow
• Build a dashboard — when your site needs auth + a database