Keep provider setup centralized
Configure Custom SMTP once in Wodby instead of repeating the same connection details across projects.
Integration
Custom SMTP integrations on Wodby
Use Custom SMTP as the SMTP relay path for OpenSMTPD and application stacks that need dependable outbound mail delivery.
SMTP
Reuse it across stacks
Attach the provider where it fits without turning each app into a custom integration project.
Keep operational control
Manage delivery, infrastructure, and third-party connectivity from one stack-aware workflow.
Supported workflows
How Custom SMTP fits into Wodby
Each supported integration kind maps Custom SMTP into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.
SMTP
SMTP
Relay outbound email through Custom SMTP from OpenSMTPD and app workloads.
- OpenSMTPD is the most direct stack-level consumer for SMTP integrations.
- Useful for transactional email flows that should route through a dedicated provider.
- Keeps provider credentials out of the application repository.
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Custom SMTP.
Stack fit
Stacks that commonly pair with Custom SMTP
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
OpenSMTPD
Stack
SMTP server stack that can relay mail directly or integrate with third-party delivery providers for reliable sending.
OpenSMTPD is the direct relay stack match for any SMTP integration.
View stackWordPress
Stack
WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.
WordPress projects often need reliable transactional email routed through a dedicated provider.
View stackDrupal 11
Stack
Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.
Drupal sites commonly centralize outbound email through a stack-managed relay path.
View stackLaravel
Stack
Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.
Laravel apps benefit from keeping mail credentials attached to the stack instead of the repo.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.