veyronn Docs

Guides

Get Started

Veyronn DocsQuickstartFaucet and First-Time FundingTrading LifecycleLive Testnet

Product

Trading

Trading TerminalMarketsPortfolio

Intent Automation

AI Intent TradingDelegated SessionsConditional AutomationStrategies and Bundles

Protocol

Core Design

ArchitectureContractsMargin and RiskTrade Settlement

Market Data

Testnet OracleCandles and Market HoursMainnet Oracle

Developers

Build

WorkspaceLocal DevelopmentChain PackageTransactions

Services

Application APIIndexerKeeper

Operations

Runbooks

DeploymentsMonitoring and IncidentsSecurity ModelMainnet Readiness

Reference

Contract AddressesMarket CatalogEnvironment VariablesGlossary

Veyronn Documentation

Deployments

Veyronn's Vercel, Railway, Robinhood Chain, and documentation deployment topology.

Production testnet topology

| Surface | Platform | Public exposure | | --- | --- | --- | | Web app | Vercel | https://veyronn.vercel.app | | BFF | Railway | /api/* and health | | Postgres | Railway | Private networking only | | Indexer | Railway | Health through BFF | | Keeper | Railway | Authenticated service access | | Contracts | Robinhood Chain testnet | Chain ID 46630 |

Vercel is the canonical frontend. Its rewrite sends /api/* to the Railway BFF. The BFF's non-API routes redirect to the matching Vercel path so there is one user-facing origin.

Secret placement

Vercel receives public chain configuration and VEYRONN_BACKEND_URL. Railway owns:

  • DATABASE_URL
  • keeper private key
  • keeper API token
  • signed-oracle key when separated
  • Pyth or Chainlink provider credentials
  • OpenAI provider key

No private service credential should use a NEXT_PUBLIC_ prefix.

Contract deployment

The testnet deployment starts at block 92429511. deployments/46630.json is committed after bytecode, references, owner, signer, keeper, market count, and oracle policy are verified.

Service order

  1. Provision Postgres and apply schema.
  2. Deploy contracts and commit the public manifest.
  3. Configure indexer from deployment block and let it catch up.
  4. Configure and fund the keeper, then verify report and automation health.
  5. Deploy the BFF and verify database, chain, price, and service reads.
  6. Deploy Vercel with public addresses and Railway origin.
  7. Run funded, realtime-oracle, and delegated-intent end-to-end checks.

Documentation

The public documentation is available at veyronn.vercel.app/docs. The Next.js app statically renders every page from mintlify-docs/ during the Vercel build, so the hosted /docs route and Mintlify use the same committed source. Documentation images are synchronized into the web build automatically.

Mintlify source lives in mintlify-docs/, with docs.json at that documentation root.

cd mintlify-docs
npx mint dev

Production publishing requires the Mintlify GitHub App to be connected to divi2806/veyronn with the documentation root set to mintlify-docs. Pushing the connected branch then creates a docs deployment.