Production readiness

Backend

A public, non-secret map of the production backend pieces Pawbi needs before TestFlight and App Store review.

Domain Plan

pawbi.app hosts this website, privacy policy, terms, support, and service status.
www.pawbi.app should redirect to pawbi.app.
api.pawbi.app should point to the production backend host and serve HTTPS.

Required DNS

Website: Route 53 alias A/AAAA records to CloudFront, or another AWS static hosting target.
API: A record to the backend Elastic IP, or an alias to a load balancer if the architecture is upgraded later.
TLS: ACM certificate for the website, and Caddy or ACM-managed TLS for the API.

Backend Health

The backend must return a successful JSON response at /health. The current app release configuration expects https://api.pawbi.app.

{
  "ok": true,
  "service": "pawbi-backend"
}

Production Secrets Checklist

Store these as AWS SSM secure parameters or another secrets manager. Do not place secret values in this website or the mobile app bundle.

DATABASE_URL with production Postgres and SSL required.
APP_JWT_SECRET as a long random production secret.
OPENAI_API_KEY for AI features.
REVENUECAT_API_KEY, webhook authorization header, and webhook signing secret.
Firebase service account values for production push delivery.
S3 pet asset bucket name and AWS permissions for private upload/read flows.
Apple bundle ID and Sign in with Apple identifiers matching app.pawbi.ios.

External Services

RevenueCat public SDK key is used by the iOS app; secret keys stay backend-only.
PostHog project token is public client configuration; avoid sending sensitive pet notes to analytics.
App Store subscriptions should use product IDs pawbi_plus_monthly and pawbi_plus_yearly.
RevenueCat entitlement should be attached to both subscription products.

Launch Verification

https://pawbi.app/privacy, /terms, and /support load over HTTPS.
https://api.pawbi.app/health loads over HTTPS.
Sign in with Apple creates and restores the same user after reinstall.
Pet records persist across logout, reinstall, and second-device login.
RevenueCat purchase, restore, webhook, and entitlement state agree between app and backend.
Push notifications work from Firebase/APNs with production credentials.