FAQ

Can't find the answer? Open a ticket and we'll reply within a business day.

What can I build?

What kinds of systems can I build on FlareX?

FlareX is organised around nine system types — pick the closest one and start from a template:

• Dashboards & admin panels — KPI dashboards, internal monitoring
• Customer portals — login portals, subscription self-serve, support centers
• APIs & backends — REST services, webhook handlers, scheduled jobs
• Internal tools — CRM, inventory, project trackers
• Discord bots — moderation, ticketing, verification, leveling
• Discord-connected dashboards — web admin panels for your community bot
• Forms & data apps — waitlists, lead capture, applications
• Websites & landing pages — marketing sites, launch pages
• Automations — cron jobs, webhook flows, cross-service syncs

See the systems quickstart for the general flow or the Discord bot quickstart for the bot-specific one. The template gallery has working starting points for every category.

Is FlareX just for Discord bots?

No — Discord bots were the original use case and remain the flagship, but FlareX is a general managed AI builder for business systems. Dashboards, portals, internal tools, APIs, automations, and websites run on the same runtime with the same isolation, billing, and database.

Can I connect to 3rd-party APIs (Stripe, OpenAI, Google)?

Yes. The 3rd-party APIs overview covers the universal pattern, and there are walkthroughs for Stripe, OpenAI, Google APIs, and Discord webhooks. For per-user auth, see OAuth. For receiving inbound webhooks, see Webhooks.

Can I bring my own domain?

Yes — Pro and Enterprise plans support custom domains. Add a CNAME, FlareX issues an SSL cert via Caddy + Let's Encrypt automatically.

Platform

Is FlareX official / affiliated with Discord?

No. FlareX is an independent platform — Discord bots are one supported use case. Your bot connects to Discord as a standard bot application using Discord's public APIs.

What languages does FlareX support?

Apps run Node.js (LTS). FlareX targets TypeScript or JavaScript. Python, Go, and Rust are on the roadmap but not supported in V1.

Can I deploy code I wrote myself (no AI)?

Partially. Every change still flows through the chat panel — the proposal model is how we enforce the sandbox and audit trail. If you have existing source, paste it into the first chat turn and ask FlareX to preserve it as-is; from there you can iterate manually with minimal AI involvement.

Isolation & security

How isolated is my app from other apps?

Each app (whether web app or bot) runs in its own Docker container with:

• Read-only filesystem
• Dropped Linux capabilities
• Strict CPU/RAM caps
• No docker-in-docker
• Docker socket access via a read-mostly socket-proxy

Network-wise, apps only reach the public internet through a custom DNS resolver that blocks DNS rebinding and private-IP lookups. Each app's Postgres schema is behind a scoped role that can't see other schemas.

Are my secrets safe?

Yes. Secrets are encrypted before persistence; the plaintext is only decrypted on the runner host when a container starts. FlareX employees can't read your secret values. We log secret create/update/delete events (not the values) in the audit trail.

What if a runner host is compromised?

All bots on that host would potentially be exposed. Runners are mTLS-authenticated to the API with cert-pinning on first heartbeat, talk to Docker via a socket-proxy, and have no privileged access to the database cluster. We also run a drain controller so a compromised runner can be retired with zero bot downtime.

AI & chat

What model does FlareX use?

FlareX uses a state-of-the-art LLM under the hood. The exact model is chosen at the platform level — we upgrade as better models become available.

Why is the chat panel different from the "free chat" box in ChatGPT-style tools?

Because the chat here is grounded in your bot's source. Proposals reference real files. Diffs are computed against the actual current version. Every accepted change becomes code the runner actually executes.

Can I use my own AI provider API key?

Not in V1. Billing flows through FlareX's metered credits.

Billing

I hit my AI credit cap. What happens?

Chat generation pauses. Your running bot doesn't notice. Options:

• Wait for next cycle.
• Enable metered overage under Settings → Billing.
• Upgrade your plan.

See Billing.

How does proration work when I upgrade?

Stripe prorates the remainder of the cycle. FlareX shows you the exact preview amount before you confirm.

Do I get refunds on downgrades?

No — the existing cycle runs out at the current tier and the new tier starts at the next cycle.

Data

Where is my data stored?

Postgres + Redis + Cloudflare R2 (object storage for log archives + bot source artefacts). Primary region is currently EU. Additional regions are added as we expand.

Can I export my workspace?

Yes — Settings → Export produces a JSON bundle of bots, configs, and audit events. Secrets are included by key (not value).

What happens when I delete a workspace?

30-day soft-delete tombstone. During that window you can restore from Settings → Deleted workspaces. After 30 days everything is permanently erased, including Postgres schemas and R2 archives.

GDPR / data subject requests?

Open a ticket referencing the workspace ID; we'll handle it in line with our privacy policy.

Ops

Where can I see if FlareX is down?

The status page shows service-level health. We're adding uptime history in an upcoming rollout.

Can I run FlareX on-prem?

Not right now. A self-hosted tier is on the roadmap for enterprise customers with compliance constraints.

Is there a Prometheus endpoint I can scrape?

Yes. Set PROMETHEUS_SCRAPE_TOKEN for your workspace and scrape https://api.flarex.app/metrics?token=<T>. See Observability once that page lands.

Feature requests

The fastest path: open a support ticket with the request and as much context as possible. We triage weekly and most ideas end up in the roadmap.