"Hello World" Examples Frameworks Examples React

Wasp Hello World

A full-stack Wasp application — React client, Node.js API, and PostgreSQL — deployed on Zerops. The client ships as static Nginx assets; the API runs on Node.js 24 with Prisma migrations.

ZCP configuration
Coding Agent
Claude Code
Subscription Login
Cloud IDE
VS Code
Public Access
Quick add
Mounted services
api dev app dev
Lightweight project core
Single dedicated container with balancers (L3/L7), logger and statistics services
apidev:3000,:3001
Node.js

Container

1Shared Core

1 GBRAM

1 GBDisk (SSD)

 GitHub repo
apistage:3001
Node.js

Container

1Shared Core

0.5 GBRAM

1 GBDisk (SSD)

 GitHub repo
appdev:3001,:3000
Node.js

Container

1Shared Core

1 GBRAM

1 GBDisk (SSD)

 GitHub repo
appstage
Static

Container

1Shared Core

0.25 GBRAM

1 GBDisk (SSD)

 GitHub repo
db:5432,:6432
PostgreSQL

Container

1Shared Core

0.25 GBRAM

1 GBDisk (SSD)

5Shared Cores

3 GBRAM

5 GBDisk (SSD)

$12.50

Per month for
Resources cost
add
FreePer month for
Lightweight pkg.

After deploying one of the environments and getting to know Zerops, you have two paths forward. 1 Clone our GitHub repositories and use the whole recipe as a template, or if you already have an existing application on a similar stack, 2 integrate the recipe setup with your application.

or
Taking ownership of theenvironment

AI agent environment provides a development space for AI agents to build and version the app. It includes dev + stage pairs for the Wasp SPA (appdev, appstage) and API (apidev, apistage), plus a low-resource PostgreSQL database.

Clone the template repositoriesPrerequisite: check authorization1Open your ZCP workspace2Start in the browser IDE3Connect from your local IDE or terminal4Work with the dev/stage flow5Move toward production
Deploy more environments

Taking ownership of the AI Agent environment

Clone the template repositories

Fork or clone the following to your local machine or GitHub account:

Prerequisite: check authorization

After you deploy the AI Agent environment, an authorization dialog should appear.

Complete the Claude Code authorization before continuing. This is separate from your Zerops access token and uses your own Claude Code subscription or API credentials.

Claude Code authorization dialog in Zerops

1. Open your ZCP workspace

The deployment creates your app services and a zcp@1 workspace.

The agent, terminal, and browser IDE run inside the ZCP service. Your app still runs in the app services, not in the ZCP workspace.

ZCP workspace service in Zerops

2. Start in the browser IDE

The fastest way to work with the agent is to open the browser IDE from the ZCP service.

  • No local setup is required.
  • The agent runs close to your Zerops project.
  • It can inspect project context and use available MCP tools.
  • After the agent makes a change, open the app URL and verify the result.
Browser IDE with Claude Code in Zerops

3. Connect from your local IDE or terminal

If you prefer local tooling, connect your machine to the Zerops project network.

Install zCLI and log in:

bash
npm i -g @zerops/zcli
zcli login <personal-access-token>

Start the VPN:

bash
zcli vpn up

Connect to the remote service:

bash
ssh -A <service-name>.zerops

4. Work with the dev/stage flow

Use the development environment for fast iteration with the agent. Use staging to verify the result before moving toward production.

Typical flow:

  1. Ask the agent for a focused change.
  2. Review and test the result.
  3. Push the change to your repository or deploy with zcli push.
  4. Verify the result in staging.
  5. Continue with the production guide when ready.

5. Move toward production

When the staging version is ready, finish the production setup:

  • configure the deployment pipeline
  • set up your domain
  • check logs and runtime behavior
  • configure backups if the recipe includes a database
  • review scaling settings before real traffic arrives
Have an app already? Integrate Zerops into it

These services were wired into Zerops with per-service integration guides. Open the Integrate flow to follow the same steps for your own application.

Deploy more environments

Deploy environments for the rest of the development lifecycle

One environment rarely tells the full story — deploy environments for other stages of development to see how they work on Zerops.

Related platform & services docs