Features / Ship to production
Shipping software usually means stitching together a source host, a CI service, a registry, a deploy tool, and a way to manage domains and secrets. Nodge is all of that in one place. You push code; the platform takes it to production.
Host your repositories on the platform with branches, pull requests, and releases. No external Git account required.
Each organization gets its own container registry. Images build and stay inside your platform.
A push runs lint, build, security scan, tests, and deploy as a single managed flow. You see each phase as it runs.
Keep separate development and production environments per project, each with its own configuration.
Add a custom domain, define routing rules, and get automatic certificates. No separate certificate management.
Encrypted runtime variables and secrets per environment, persistent volumes, and project backups are part of the platform, not bolted on.
Keep an external mirror of any repository if you need one.
From commit to live URL, in one platform.
The platform runs lint, build, security scan, tests, and deploy as one managed pipeline, taking your commit to production.
No. Both are built in. Each organization gets its own repositories and its own container registry.
Yes. Each project can have separate environments, each with its own configuration and secrets.
You add a domain and define routing rules, and certificates are issued automatically. There is no separate certificate management.
They are encrypted per environment and applied to your app on deploy.
Yes. You can mirror any repository in or out.
