useSend
Self-hosted email campaign and transactional messaging application.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Application platform deployment; Docker / Compose
Runs in
Documented customer environment
useSend application, PostgreSQL, queues and AWS SES/SNS integration.
- Hostinger: Customer VPS account
- Railway: Customer platform workspace
- Railway
- Hostinger
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- Hostinger: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Hostinger ↗ · Source checked 2026-11-19
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Railway ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Application platform deployment; Docker / Compose |
|---|---|
| Infrastructure | Servers / containers useSend application, PostgreSQL, queues and AWS SES/SNS integration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The self-hosting guide documents GitHub login; published v1.10.4 code also registers Google when configured. The code permits an initial bootstrap account, then requires an existing account or team invitation. Configure provider credentials, trusted email/account linking and callbacks. Email codes, SES credentials and API/SMTP tokens are separate; generic SAML/OIDC federation is not established.
Named external login providers for the self-hosted application, with published account-admission behavior · Source ↗ · Published v1.10.4 provider and account-admission code ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official production Docker guide links a Compose stack; the v1.10.4 recipe includes the app, PostgreSQL, Redis and RustFS image storage. Pin the application image instead of latest and configure provider login, secrets, persistent data and TLS. AWS SES/SNS delivery and optional public image URLs require separate configuration; the SMTP proxy is a different service.
Published application stack, distinct from the separate SMTP-server Compose example · Source ↗ · Deployment artifact ↗ (v1.10.4 (application image tag is latest; pin a compatible deployment version)) · Official self-hosting dependencies and settings ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The official guide establishes an app, PostgreSQL, Redis, SES/SNS and optional image-storage topology but no complete production CPU/RAM/storage minimum. Size campaign volume, queue concurrency, email-content retention and storage before selecting instances; 100 internal users and 1 TB alone do not specify delivery throughput or HA capacity.
Current self-hosted topology; whole-system production sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
useSend; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream v1.10.4 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
useSend upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
Community & maintenance
The reviewed upstream contributor history includes KMKoushik, harshsbhat, magicspon, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Marketing automation
- Self-hosted email campaign and transactional messaging application.
Compare within Marketing automation
- Apache UnomiApache customer-data platform for event profiles, segmentation and personalization.
- Azure
- BillionMailCustomer-operated mail server and marketing application.
- Azure
- DittofeedSelf-hosted customer engagement and messaging orchestration platform.
- Railway
- Render
- Hostinger
- erxesCustomer-operated business and customer engagement platform.
- Railway
- EspoCRM Self-HostedSelf-hosted CRM with sales records, customer-service features and email campaign management.
- Railway
- MailWizzCommercial self-hosted email marketing application.
- AWS
- DigitalOcean
- Linode
- Mautic Self-HostedSelf-hosted marketing automation for email campaigns, lead nurturing, forms and landing pages.
- AWS
- DigitalOcean
- Linode
- phpListCustomer-operated mailing list and email campaign manager.
- AWS
Showing 8 of 11 other listings in Marketing automation. These products address related workflows; read their category-fit notes before comparing scope. See all of Marketing automation →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Hostinger ↗www.hostinger.com
- Railway ↗railway.com
- GitHub LICENSE (AGPL-3.0) ↗raw.githubusercontent.com
- GitHub Releases ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Hostinger ↗ · Hostinger
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
- Railway ↗ · Railway
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
- Hostinger ↗ · Hostinger
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com