Zerops for Pulumi

Deploy your application to Zerops using Python, Go, C#, Java, TypeScript or YAML. Keep application infrastructure alongside your code, preview changes, and deploy with pulumi up.

Start with zerops-app / WebApp: one component creates a project, an application service, an optional PostgreSQL database, a deployment and a public URL. Use zerops primitives when you need direct control over services, storage or networking. The primitive provider bridges the Zerops Terraform provider; you do not need Terraform installed.

Start in your language

Python · Go · C#/.NET · Java · TypeScript · YAML

Each starter deploys the same small Python web application. The language you use to describe infrastructure does not dictate your application's runtime. Only your chosen infrastructure language and the Pulumi CLI are needed locally; Zerops builds and runs the application.

For example, after choosing a state backend:

pulumi new https://github.com/zeropsio/pulumi-zerops/tree/v0.1.1/templates/zerops-python
pulumi config set --secret zerops:token
pulumi up
pulumi stack output url

The template also prompts for a secret Zerops token and an explicit appName. PostgreSQL is off initially; enable it with pulumi config set database true, then run pulumi up again. Review costs before deploying; resources run until you remove them. Run pulumi destroy when finished (this deletes application and database data).

Packages and compatibility

Both packages are version 0.1.1. The component SDK brings in the primitive SDK as a dependency.

Go modules use release tags sdk/v0.1.1 and sdk-app/v0.1.1; use @v0.1.1 in go get, not the tag's directory prefix. The replace directives in components/go.mod and sdk-app/go.mod are for monorepo development. Go ignores dependency modules' replacements, so consumers never inherit them.

Python requires >= 3.10. Go modules currently require Go >= 1.26.6. The .NET SDK targets net6.0 and works with .NET 8 and 10; templates target .NET 8. Java SDKs compile with JDK 21 and emit Java 11-compatible bytecode; examples and templates target Java 17. Node.js 22 LTS is the tested Node runtime.

What WebApp creates

A LIGHT project with an explicit name, a single-container runtime service, optional PostgreSQL, environment variables, a directory deployment, and public subdomain access after deployment. It does not allocate dedicated IPv4. The optional default database is postgresql:single@16, with a 2 GB minimum disk. This is a small, non-HA starting point, not a free tier or a production availability promise. For HA, explicitly set databaseType to postgresql:ha@16; availability and price differ. See Zerops pricing.

Database connections use server-side references: DATABASE_URL, DB_HOST, DB_USER, DB_PASSWORD, and DB_NAME reference database service values; DB_PORT is the literal 5432. The component never reads resolved credentials back. It exports connection variable names, not passwords. See the component reference.

Deployment and secrets

• WebApp.source and primitive ServiceDeploy.sourceDir are directory paths, not Pulumi archives. Relative paths resolve from the Pulumi program directory.
• The directory is uploaded as-is except every .git directory. Curate app/: do not include secrets, .env, node_modules, .venv, or build caches. .gitignore is not an upload filter.
• Source changes replace ServiceDeploy, meaning a new deployment. Destroying only that resource does not roll back the app. Destroying its service/project cleans up the environment.
• Secret configuration and secret resource values are encrypted in Pulumi state, not omitted from it. Protect state backups and your backend's encryption keys/passphrase. Do not export secrets as ordinary stack outputs.
• Zerops builds asynchronously. If deployment fails, open the service's build log in the Zerops GUI for the actual build error.

Primitive resource map

The schema contains 19 resources. The short YAML forms below correspond to canonical tokens such as zerops:index/project:Project.

There are 9 data functions, plus the bridge's provider-bound terraformConfig method (not a Zerops lookup).

Provider configuration

Managed-service floors are applied at preview and reject smaller configured values. RAM overrides must be finite positive numbers with at most three decimal places. Dual-mode managed types require an explicit :single@ or :ha@ mode. When upgrading existing shorthand state, set type to the qualified value already recorded in base to avoid replacement; choosing the other mode replaces the service.

More information

• Installation, authentication and provider configuration
• Primitive package overview and WebApp component overview
• Working primitive examples and application starter templates
• Changelog, contributing, and private security reporting