Describe what the bot should do and you get a TypeScript project back. One file per command, one per event, typed strictly, written against the current discord.js release.
Four checks run before you ever see it. It has to compile. It gets scanned for the API that was removed or deprecated in v14, the kind that still looks correct in an editor and then fails at runtime. Fourteen structure rules check that the project is actually a project: entry point present, dependency declared, no bot token pasted into a file, no 400 line monster holding six commands. Then it starts, in an isolated container with no network, and has to get as far as logging in. When a check fails it goes back and fixes it, up to three rounds, and you watch that happen line by line.
There are two targets. A normal Node bot you host anywhere, or a resource that runs inside your FiveM server. The FiveM one is the interesting half: one process instead of two, no second host to pay for, and it reads the live player list directly instead of asking your server over HTTP. Six of the structure rules exist only for that target, because the manifest, the Node version and the CommonJS setup are each a way for a resource to silently never start.
The code is yours. Download the project and it runs on your machine with your token, with no account here.
Your first build is free. After that the builds we have measured came in around 80 credits, and a change to a finished bot around 110.
Every build is compiled, scanned for dead API and started in a sandbox before you see it. What that cannot cover is your own token against your own server, so if something surprises you there, the report button on any page is the fastest way to reach us.