What to compare
- job and deployment constraints
- current limits and billing units
- identity and secret ownership
- backup and export path
- failure and migration procedure
Read the sources
Cloudflare Workers ↗
Application hosting documentation for request handlers and related Cloudflare services.
Public documentation; deploying an application requires an account and explicit resource authority. Check runtime limits, bindings, billing and migration constraints for the actual workload.
Cloudflare R2 ↗
Object-storage documentation for application files, datasets and media.
Public documentation; bucket access and writes require scoped credentials. Storage does not establish content rights. Compare operations, retention, integrity checks and delivery controls.
Fly.io ↗
Application and Machine documentation for workloads needing process and filesystem control.
Public documentation; deployment and resource changes require account authority. Compare persistent storage, backups, regions, resource limits and operating costs for the chosen workload.
Resend ↗
Transactional email integration documentation for application messages.
Sending requires a configured account, verified sender and an authorized message. A delivery integration is not consent to marketing. Check suppression, unsubscribe and provider requirements.
Better Auth ↗
Application authentication documentation covering a self-managed integration and supported features.
Public documentation. Select and test the database adapter, account recovery and session settings. A library installation is not a secure migration. Test identity ownership, revocation and account linking.
When to look again
At initial design and during reviews of cost, reliability, customer requirements or migration needs.
Give your agent this question
Compare two workable stacks for the supplied constraints. Assign one owner to login, email, compute and storage; cite current limits and explain what remains custom. Do not create accounts or spend money.