Server builder · Discord
FTA Bot
From The Ashes: a way to design a Discord server in plain language, inspect the plan, and keep the final decision with an administrator.
Closed beta
A controlled build
Describe it. Preview it. Approve it.
Use /fta build with a description or a preset. FTA validates the proposed structure and shows what would change before it makes changes to Discord.
Start with words or presets
Choose from community types, Basic/Medium/Advanced depth, and optional Events, Staff HQ, or FlowTrack areas.
See the whole layout
Review roles, channels, topics, forums, ordering, and permissions. Revise the plan or run a dry run first.
Approve the exact plan
Validated, deterministic code applies the approved changes. Ordinary builds reconcile existing structure and do not delete channels or roles.
What it handles
Structure without surrendering control.
- Discord foundationsRole hierarchy, categories, text and voice channels, descriptions, ordering, and permission overwrites.
- Community layoutsPresets for general, gaming, creator, learning, local, men's, and women's communities. Advanced layouts can include forums when the server supports them.
- Existing serversInspect and reconcile before making changes. Normal builds are non-destructive by default.
- Owner-only maintenanceSeparate backup, cleanup, and full-reset commands require extra review and confirmation. Backups are JSON exports; one-click restore is not available yet.
Alongside FlowTrack
Build the space, then support the people in it.
An optional FlowTrack-ready layout can prepare channels and roles. FlowTrack still configures independently and works without FTA.
Safety boundary
Server owners keep the final say.
FTA needs Discord structure permissions to carry out approved actions. OpenAI proposes natural-language plans but does not directly execute changes. Admins should test in a disposable server, inspect previews, download backups when appropriate, and understand that permanently deleting a Discord channel also deletes its message history.