
Deploy HappyView
A lexicon-driven ATProto AppView.
Just deployed
/var/lib/postgresql/data
Just deployed
Just deployed
Just deployed
Deploy and Host HappyView on Railway
HappyView is a lexicon-driven ATProto AppView. Upload lexicon definitions at runtime and HappyView dynamically generates XRPC query and procedure endpoints, indexes records from the network, and proxies writes to users' PDSes — no restart required.
About Hosting HappyView
Hosting HappyView requires a Postgres database, an AIP instance for OAuth 2.1 authentication, and a Tap instance for syncing records from the AT Protocol network. This template deploys all four services pre-configured to work together. After deployment, you'll need to assign public domains to HappyView and AIP, set your admin DID, and generate signing keys for AIP. See the quickstart guide for setup steps.
Common Use Cases
- Building custom ATProto applications with their own record types and queries
- Indexing and querying AT Protocol records without running a full relay
- Hosting a backend for ATProto clients that need OAuth authentication and record management
Dependencies for HappyView Hosting
- PostgreSQL 17+
- AIP (ATProto Identity Provider) for OAuth 2.1 with PKCE and DPoP
- Tap for syncing AT Protocol records from the network
Deployment Dependencies
- HappyView documentation
- AIP configuration guide (signing key generation)
- AT Protocol specification
Why Deploy HappyView on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying HappyView on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
ADMIN_DIDS
Comma-separated list of DIDs with admin access to the AIP server
OAUTH_SIGNING_KEYS
Private keys for signing OAuth tokens (base58-encoded); see the AIP docs for details
ATPROTO_OAUTH_SIGNING_KEYS
Private keys for signing ATProto-specific OAuth tokens (base58-encoded); see the AIP docs for details

