Integrations
Drop-in vendor adapters useDeploy ships out of the box. Each page is the operator's playbook for one third-party service wired to a bounded context.
UseDeploy ships several modules already wired to popular vendors. The adapters live in the bounded context that owns the concern, behind a port the rest of the codebase consumes — so swapping providers is a single-file change.
Available integration playbooks
| Pair | Bounded context | Status |
|---|---|---|
| Polar (billing) | modules/billing | Operator playbook lives under Deploy |
| Railway (deploy) | infra | Operator playbook lives under Deploy |
| Sentry (errors) | infrastructure/observability | Stub — fill in details |
| UploadThing (storage) | modules/storage | Stub — fill in details |
| Resend (transactional email) | modules/notifications | Stub — fill in details |
Each integration page covers env vars, the relevant port/adapter file path, the dashboard configuration, and the smoke test you can run after wiring it up.
Polar.sh
Sell digital products via Polar.sh through the canonical IPaymentProvider port. Same architecture used to sell UseDeploy itself, ready for any boilerplate buyer to use for their own products.
Sentry
Wire Sentry as the error reporter for both the Bun + Express server and the Next.js client. Server uses @sentry/bun, client uses @sentry/nextjs.