Your Node.js project, beyond your laptop.

Prepare an Express API, a background worker or a Discord bot. One process, declared dependencies and a resource budget you control.

A predictable start

Include package.json, a start script and a lockfile. Install locally, test npm start and commit the generated lockfile. Do not upload node_modules: native dependencies may differ on the hosting system.

HTTP is not a Discord gateway

An API needs an assigned HTTP port and routing. A Discord bot normally opens an outbound gateway connection instead. Our Express starter listens on localhost for safe local testing; for hosting, listen on 0.0.0.0 and SERVER_PORT and enable HTTPS routing in Domains.

Keep state outside process memory

Restarting clears in-memory objects. Put durable records in a database or designated persistent files. Environment variables configure the app; they are not a database. Back up important data separately.

Measure before growing

CPU-heavy synchronous work can block the event loop. RAM depends on caches, dependencies and traffic, not the language alone. The simulator checks plan budgets, not requests per second.

A small community API

GET /health
→ { "status": "ok" }

GET /api/greeting?name=Botkeep
→ { "message": "Hello, Botkeep!" }

Included in the Express starter. No account system or database is implied.

Plan your resources

Try a concrete starting point

APIs

Express API

A small JSON API with health checks, input validation and graceful shutdown.

6 files · instructions includedExplore project

Bots

discord.js · /ping

A working slash-command bot with explicit registration and clean shutdown.

7 files · instructions includedExplore project

Enabled profiles can be deployed from the panel. Configure addresses and HTTPS in Domains; a custom domain requires DNS verification. No performance or availability guarantee is implied.