stayers.funTechnical Architecture
Vercel handles the website; the N95 owns persistent analytics and accounting.
Code exists; Stayers production behavior is not yet verified.
The monorepo separates stateless website work from durable background services.
Components
| Location | Responsibility |
|---|---|
| apps/web | Next.js frontend, wallet requests, transaction review/confirmation and private API bridges |
| apps/server | Node API, PostgreSQL accounting, read-only indexer and survival services |
| packages/core | Meteora DBC/DAMM integration, validation and transaction builders |
| packages/shared | Shared transport validation and experimental policy definitions |
| infra | Docker Compose, PostgreSQL volume, backups, tunnel and policy configuration |
Transaction path
Wallet-signed launch/trading preparation stays on the Vercel side where possible, using the private mainnet RPC configuration. The browser approves the exact reviewed transaction. The N95 does not sign or submit transactions.
A backend outage can affect discovery, chart history and survival information without requiring the trading path to use a mock fallback.
Persistent services
The N95 code includes historical backfill, confirmed notifications, finalized transaction checks, deduplication, checkpoints, retry/backoff, candles and metrics. Financial receipts enter the same PostgreSQL ledger used for revenue classification and reconciliation.
PostgreSQL is private to Docker networks. Vercel reaches only the restricted HTTPS API through Cloudflare Access and Tunnel. DATABASE_URL belongs only in the N95 environment.
Deployment evidence
The architecture is implemented and fixture-tested. Docker/N95 runtime and the live Cloudflare connection remain unverified. The N95 is not advertised as an operational production service until those checks pass.