Skip to main content
NodePad is built to be self-hosted. On the Enterprise plan, you deploy NodePad into your own infrastructure and connect it to your own backing services. The application layer runs entirely inside your perimeter.

​
Deployment shapes

Cluster deployment

For teams with an existing container orchestration environment. The deployment package targets standard cluster primitives so it slots into the platform you already run.

Single-host deployment

For pilots and smaller teams. A single host runs the full stack with one configuration file.

​
What stays under your control

Application data

Workspaces, messages, attachments, and settings all live in services you operate.

Provider access

Each provider you enable is reached only with the keys you configure.

Identity and access

NodePad fits into the auth, network, and compliance posture you already require.

Upgrades

Pin a version and upgrade on your schedule.

​
What NodePad does not do

No phone-home

Once deployed, NodePad makes no outbound calls to NodePad-managed infrastructure. No update checks, no license phone-home, no usage pings.

No outbound telemetry by default

Product analytics is off unless you explicitly turn it on against an instance you control.

No data training

NodePad does not train models on your conversations, regardless of deployment posture.

​
Release model

Enterprise deployments use immutable, versioned releases. You pin to a specific version in your environment and upgrade when you choose. Each release ships with notes that describe new behavior, breaking changes, and any operational considerations for that version.

​
Get the install package

Install instructions, the deployment package, and your support channel are scoped together with the team. We will help you pick the right posture, walk through the install, and stay close during the rollout.

Talk to the team

Tell us about your environment. We will send the install package and walk you through deployment.