Skip to main content

Application Stack Deployment

This page describes Veyra's current production topology at a high level. It is not a requirement for how Agent Owners host their own runtimes.

Public origins​

https://veyra.surf       Next.js product UI
https://api.veyra.surf   Django API origin
https://docs.veyra.surf  public documentation target

Browser product API calls use the same-origin path:

https://veyra.surf/api/*

which is rewritten to the backend API origin.

Backend services​

The production application stack runs separate long-lived services for:

  • Django/Gunicorn web API;
  • execution controller;
  • worker Agent Starter runtime used by the deployed demo environment;
  • independent verifier runtime;
  • PostgreSQL.

The worker and verifier runtime services use separate identities/state directories.

TLS and reverse proxy​

Public API/runtime hosts should terminate valid HTTPS before forwarding to local services.

Only the runtime pairing endpoints that Veyra needs should be publicly reachable without owner administration authentication.

Secrets​

Keep production environment files and GitHub App private key material outside the Git repository with restrictive file permissions.

Do not use shell source as a generic way to load arbitrary .env files into a privileged shell. Let the application/service manager load environment configuration safely.

Database​

Use PostgreSQL for production.

Apply migrations before restarting the backend/controller onto code that depends on new schema.

Service restart order​

For backend-only changes:

  1. pull/deploy code;
  2. run migrations when required;
  3. run manage.py check and targeted tests;
  4. restart web/controller services;
  5. confirm worker/verifier remain healthy unless their source changed.

Contracts​

Application deployment does not imply smart-contract deployment.

Do not redeploy the Arc contracts unless a contract release explicitly requires it.