Deploy and Host

Deploy a self-hosted PDPP Core reference node on Railway.

About Hosting

This template runs the open-source PDPP reference implementation in your Railway account. It creates one public operator console, one private Authorization Server / Resource Server service, and durable Postgres storage. It is not a hosted PDPP service operated by Vana or OpenDataLabs.

Why Deploy

Use this when you want a personal PDPP Core node that can issue scoped grants and serve grant-scoped record queries over HTTPS. Browser-backed connectors are intentionally outside this Core template; they run through local collectors or explicit browser profiles.

Common Use Cases

• Inspect and operate a personal PDPP reference instance.
• Test owner-gated dashboard access and OAuth / MCP grant flows.
• Query a small hand-imported record set over the public composed origin.
• Use the same Core topology before adding connector collection later.

Dependencies for

PDPP Core needs a public HTTPS console, a private AS/RS service, and durable storage. This template uses pinned public GHCR images and Railway Postgres.

Deployment Dependencies

• Railway account with capacity for two app services and one Postgres service.
• A strong PDPP_OWNER_PASSWORD set when Railway prompts for variables.
• The same PDPP_OWNER_PASSWORD value on both app services.
• PDPP_DATABASE_URL is wired to the Postgres service by Railway.

After deploy, open the console public domain and sign in as owner. To run the protocol smoke from a repo checkout:

node scripts/railway-mcp-query-smoke.mjs \
  --origin https:// \
  --owner-password "$PDPP_OWNER_PASSWORD"