Dittofeed
Self-hosted customer engagement and messaging orchestration platform.
6 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
Dittofeed application, PostgreSQL, ClickHouse and supporting services.
- Render: Customer platform workspace
- Railway: Customer platform workspace
- Hostinger: Customer VPS account
- Railway
- Render
- 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
- Render: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
> ## Documentation Index > Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt > Use this fil ↗ · 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
- 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
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 Dittofeed application, PostgreSQL, ClickHouse and supporting services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | MIT 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.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
OIDC-based multi-tenant authentication is documented, but the detailed guide restricts that mode to dittofeed-ee and Dittofeed Cloud. The community lite deployment instead offers a shared-password single-tenant mode. Obtain the Enterprise image/entitlement and configure provider claims and workspace access; anonymous demo mode is unsuitable for production.
Self-hosted Enterprise OIDC versus community/lite authentication; detailed mode restrictions override the general overview · Source ↗ · Authentication-mode overview ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official Docker guide links the lite Compose stack and documents replacing default credentials, secrets and dashboard URLs. It includes PostgreSQL, ClickHouse and workflow services; the vendor also publishes a Helm chart. Choose a compatible pinned release and configure storage, TLS, authentication and backups; Enterprise uses a separately entitled image.
Vendor community/lite deployment recipe, distinct from Enterprise image delivery · Source ↗ · Deployment artifact ↗ (main (moving branch; pin compatible application and dependency versions)) · Official Kubernetes/Helm recipe ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Helm guide lists application-container requests/limits of 1 CPU and 512 MiB RAM and ClickHouse memory requests/limits of 1 GiB. These are component configuration defaults, not a whole-stack minimum: PostgreSQL, Temporal, storage, replicas and traffic need separate capacity. They do not size 100 users, 1 TB or HA.
Documented chart component allocations, not total host or production capacity · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Dittofeed; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 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.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
Community & maintenance
The reviewed upstream contributor history includes maxgurewitz, chandlercraig, neo773, 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 customer engagement and messaging orchestration platform.
Compare within Marketing automation
- Apache UnomiApache customer-data platform for event profiles, segmentation and personalization.
- Azure
- BillionMailCustomer-operated mail server and marketing application.
- Azure
- 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
- SendPortalSelf-hosted email marketing, subscriber and campaign management.
- Railway
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
- > ## Documentation Index > Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt > Use this fil ↗docs.dittofeed.com
- Railway ↗railway.com
- Hostinger ↗www.hostinger.com
- Render Guide ↗docs.dittofeed.com
- GitHub LICENSE (MIT) ↗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.
- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil ↗ · Render
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
- Railway ↗ · Railway
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
- Hostinger ↗ · Hostinger
Provider guide · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil ↗ · Render
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com