NIRODEX / GETTING STARTED
Less setup. More building.
Your workspace is the home for your projects, services and shared billing.
From an idea to a running service
Create an account to get a personal workspace. Create a project; its production environment is ready automatically. Choose Create service and pick a Discord bot, website/application, or database. Templates create working starting points. Review the plan, then deploy a free instance or complete a paid service's invoice.
Bring your files, image, or repository
Files use Node.js, Bun, Python, Java, or static Nginx runtimes. Upload application files and enter an ordinary command such as node index.js or python main.py. Java needs your own JAR. Bind web servers to 0.0.0.0 and the PORT variable. Container images run unprivileged with a read-only root. GitHub deployments require an installed GitHub App and the platform's isolated builder; GitHub login alone does not grant repository access.
Related services, together
The project canvas shows actual services and connections derived from environment variable references. Drag cards to organize them, or switch to the accessible list. Each environment has separate configuration, private networking, instances, and data. Empty environments are free. Creating another paid instance requires a new price review. Configuration recipes never copy production secrets or data.
Save changes. Review. Deploy.
Configuration edits are saved as drafts. Review the source, command, variable keys and networking changes, then deploy. Secret values are encrypted at rest and masked in the editor. A reference such as ${{postgres.DATABASE_URL}} resolves only within the current environment; missing references and cycles are rejected. Deployment history shows execution, logs and failures. Rollback restores a previous code/configuration revision while retaining current volume and database contents.
Code and persistent data have different jobs
The Files tab edits staged application code. Deploy files publishes a versioned snapshot mounted read-only at /app. Write runtime data under /data; it survives redeploys and code rollback. The selected disk quota covers the instance's code snapshots and persistent data. Included backups capture the stored instance data; restoring a backup restores that snapshot's contents. Deleting a service explicitly removes files, volume, backups and archives.
Private by default where it matters
Database templates generate passwords and connection URLs. PostgreSQL and Redis remain private unless you explicitly enable public TCP networking. Applications and databases in an environment share an isolated network and stable service discovery. Public application HTTPS and verified custom domains require the platform's routing gateway, DNS and TLS setup. The interface reports pending routing rather than promising an available endpoint before setup.
A plan, not a consumption meter
Compute is billed for allocated CPU, RAM and disk at the chosen monthly or yearly price. Resource graphs are monitoring information. Stopping compute keeps the paid reservation and recurring bill. Review proration before upgrading; payment must settle before resources grow. Downgrades queue at renewal with disk safety checks. Cancellation ends renewal at the paid period boundary; it does not immediately delete data.
One workspace credit pool
Add prepaid service credit through Stripe. Credit is granted only after verified successful payment, including delayed payments. Credit applies against the full service invoice after tax; it is not a discount. Stripe applies the shared balance to eligible upcoming invoices and attempts any remainder on an authorized default saved payment method. Fully credit-funded invoices need no card. Already finalized invoices have a payment link; adding credit does not promise to retroactively pay them. Credit is nontransferable and has no cash-withdrawal feature.
Free renewal and payment recovery
One free instance is allowed per billing owner across all workspaces and environments. Renew every 72 hours using the configured sponsorship flow. Expired instances hibernate with files archived; renewal restores them when capacity is available. Paid renewal failures have a seven-day grace period before suspension; files are preserved for recovery. Refunds and disputes reverse top-up credit, and spent credit may become debt that restricts new purchases. No ordinary payment retry deletes hosted files.
A workspace for your people
Owners manage ownership; owners and admins manage billing and invitations. Members manage workloads. Viewers can inspect status and metrics while secret-bearing configuration, files and console access require write permission. Copy-link invitations expire in seven days and can be used once. A workspace always retains at least one owner.