DB Ware Company does not intermediate your email traffic.
After deployment, messages do not need to pass through DB Ware Company servers. Domain, IP, reputation, queues and operating capacity belong to the customer environment.
Ware SendEmail Delivery Engine for Self-Hosted Infrastructure
WARE SEND • DELIVERY ENGINE
An email engine designed to run inside your company infrastructure.
DB Ware Company licenses, deploys and integrates Ware Send in the customer environment. After handoff, your application sends through your own domain, IP, queue and server without requiring DB Ware Company infrastructure to transport the messages.
Deployed software
Customer infrastructure
Operation under your control
customer-infrastructure / waresend-node
SELF-HOSTED
OPERATING MODEL
You acquire the engine. The operation stays in your infrastructure.
Ware Send is not a hosted sending plan operated by DB Ware Company. It is infrastructure software installed in the environment defined by the customer and integrated with company applications.
Licensing and deployment
The project covers the engine, deployment, configuration and integration. Support and future upgrades can be contracted separately.
The premise
Stop turning volume growth into automatic billing growth.
Companies running high-volume applications can operate the engine inside their own environment and size servers, IPs and capacity according to technical and governance requirements.
What you need to provide
1 domain
A domain you control for sending identity and authentication. Example: company.com.
1 VPS or cloud
Linux server with a public IP and resources sized for the project volume. Infrastructure is contracted and owned by the customer.
Your application
ERP, SaaS, fintech, e-commerce, billing platform, marketplace or any system that needs to send email.
DELIVERY ARCHITECTURE
From application to recipient MX, inside an environment your company controls.
Illustrative architecture: the engine runs in the customer environment and delivers directly to recipient servers.
DELIVERY ARCHITECTUREFrom application to recipient MX, inside an environment your company controls.
SELF-HOSTED
Authenticated ingress
Processing
Delivery
DKIMSPFDMARCTLS
Shared content and attachment: one copy
Active window controlled by the Engine
Light work does not wait behind heavy work
DELIVERY PIPELINE
- accept + persist
- classify + sign
- release MTA window
- SMTP/TLS + retry
CURRENT FLOW 01
The API authenticates, validates and persists the operation while shared content, attachments and recipients are kept separate to avoid unnecessary duplication.
Illustrative architecture: the engine runs in the customer environment and delivers directly to recipient servers.
INFRASTRUCTURE SIZING
VPS × volume reference
Ware Send uses the real capacity of the environment and does not impose an artificial message-count ceiling. The ranges below are starting points for a single-company operation with a controlled active queue, shared content and dynamic work release.
WARE SEND / VPS SIZING
APPROXIMATE PLANNING RANGES · VOLUME IS NOT AN ENGINE LIMIT
VPS sizing
| Volume reference | Starting CPU | Starting RAM | Suggested SSD/NVMe |
|---|---|---|---|
| 100k | 1 vCPU | 2 GB | 20–30 GB |
| 500k | 1–2 vCPU | 2–4 GB | 20–40 GB |
| 1M | 2 vCPU | 4 GB | 30–50 GB |
| 2M | 2–4 vCPU | 4–8 GB | 40–80 GB |
| 5M | 4 vCPU | 8 GB | 60–120 GB |
| 10M | 4–8 vCPU | 8–16 GB | 100–250 GB |
Storage ranges are approximate operating headroom for the active queue, logs, temporary data and attachments. Shared content and attachments should not be duplicated per recipient. Long defer periods, large messages or a larger active queue window may require more space.
ADAPTIVE ENGINE
The VPS sets the pace; Ware Send manages pressure.
Adaptive Engine observes CPU, RAM, I/O, free disk, backlog, message cost and drain capacity. It accelerates with headroom and, under pressure, slows heavy work, keeps lightweight messages moving and applies backpressure to preserve service stability.
Large operations can register millions of recipients as one job. Shared content and attachments are preserved once; the Engine materializes only the window the VPS can process at that moment.
COMPATIBLE INFRASTRUCTURE
Choose where to host it. Ware Send is not tied to one provider.
Use the official links to compare VPS and cloud options. The choice depends on region, capacity, support, network and infrastructure strategy — not on a Ware Send commercial plan.
CLOUD / VPS
Hostinger
CLOUD / VPS
KingHost
CLOUD / VPS
Contabo
CLOUD / VPS
Hetzner Cloud
CLOUD / VPS
OVHcloud
CLOUD / VPS
DigitalOcean
VPS/cloud infrastructure is contracted and operated by the customer. The links below are infrastructure references for evaluation and validation only.
End-to-end implementation
You do not receive an installer and a task list. DBWare performs the implementation.
With customer-authorized access, our team prepares the environment, configures the email identity, installs the engine and performs delivery tests before production handover.
01
Technical planning
We validate domain, VPS/cloud, public IP, estimated volume, source application and integration method.
02
Identity and DNS
We create the engine hostname, such as mail.company.com, and configure/guide A, PTR, SPF, DKIM and DMARC.
03
Engine and security
We install Gateway, MTA/Postfix, DKIM signing, TLS/HTTPS, token authentication, queues and runtime services.
04
Infrastructure validation
We test DNS resolution, reverse DNS, certificate, DKIM, SPF, DMARC, queue, SMTP egress and service health.
05
Integration
We deliver documentation and examples for REST API and, when included in scope, authenticated SMTP.
06
Operational handover
We perform real test emails and hand over a working infrastructure with project credentials and documentation.
Customer-owned identity
Your domain, your IP, your queue, your reputation and your operation.
DBWare acts as solution provider and implementer. The infrastructure does not need to route customer messages through DBWare after handover.
Own hostname
Example: mail.company.com, connected to the customer environment.
Own PTR
The IP reverse DNS is aligned to the hostname defined for the engine.
Own authentication
SPF, DKIM and DMARC are configured for the customer domain identity.
Own credentials
API token and technical credentials remain in the environment delivered to the customer.
Real-world applications
Built for systems that cannot depend on a mailbox to send.
The platform supports transactional flows and large application-generated batches.
Invoices and collections
Password resets
Security codes
Account confirmation
Payment confirmation
Invoices, XML and documents
Operational alerts
Automated reports
ERP/SaaS notifications
High-volume campaigns and batches
Marketplaces and e-commerce
Fintech and billing platforms
USE ECOSYSTEM
One engine for multiple email workloads inside your architecture.
Ware Send owns the delivery layer. Your application still decides recipients, timing and message content.
Transactional email and automation
Transactional email, email notifications, sign-up confirmations, password reset, OTP and security codes, billing, documents, system alerts and automated messages generated by ERP, SaaS, fintech and e-commerce applications.
Own SMTP, relay and email API
Own SMTP server, SMTP relay, email gateway, REST email API, MTA/Postfix, persistent queue and self-hosted infrastructure on VPS, cloud or dedicated Linux servers.
High volume, bulk email and campaigns
Bulk email, mass sending, batches, newsletters, campaigns and email-marketing infrastructure can use the engine as a delivery layer. Segmentation, consent, opt-in and unsubscribe logic remain in the customer application.
Deliverability, identity and reputation
DKIM, SPF, DMARC, PTR, reverse DNS, TLS, IP and domain reputation, warm-up, hostname and authentication are part of the technical delivery design.
IMPLEMENTATION PRICE
Ware Send in your infrastructure for R$ 14.999,90.
The implementation price is fixed in Brazilian reais. USD and EUR below are reference conversions calculated automatically through DB Ware’s FX API.
implementation price
Buy
USD reference
—
—
EUR reference
—
—
Showing the latest available FX quote
What this price represents
Ware Send implementation in the environment defined for the project, including product updates with fixes and improvements. VPS/cloud, IPs, infrastructure services, ongoing support and custom evolutions follow the contracted commercial scope.
USD and EUR conversions are indicative. The implementation is billed in BRL.
MARKET REFERENCE
Ware Send × SendGrid: different billing models.
Ware Send has an implementation price in the customer environment. SendGrid is a recurring SaaS service priced by plan/volume. The table uses public SendGrid Email API prices only as a commercial reference.
| Solution | Plan / volume | Public price | Billing |
|---|---|---|---|
| Ware Send | Implementation in customer environment · Capacity sized by infrastructure | R$ 14.999,90 | One-time |
| SendGrid Email API | Essentials · 50.000 emails | US$ 19.95/mo | Recurring SaaS |
| SendGrid Email API | Essentials · 100.000 emails | US$ 34.95/mo | Recurring SaaS |
| SendGrid Email API | Pro · 100.000 emails | US$ 89.95/mo | Recurring SaaS |
| SendGrid Email API | Pro · 300.000 emails | US$ 249.00/mo | Recurring SaaS |
| SendGrid Email API | Pro · 700.000 emails | US$ 499.00/mo | Recurring SaaS |
| SendGrid Email API | Pro · 1.500.000 emails | US$ 799.00/mo | Recurring SaaS |
| SendGrid Email API | Pro · 2.500.000 emails | US$ 1,099.00/mo | Recurring SaaS |
SendGrid prices are taken from its public official pricing table and may change, include taxes or additional conditions. This compares commercial models, not functional equivalence.
View official SendGrid referenceEconomic model
Compare recurring volume-based cost with private infrastructure.
The providers below represent familiar market models. Prices, limits and features change by plan and region, so the most relevant comparison is with your own current bill.
Managed delivery service
Delivery infrastructure belongs to the provider and contracts typically scale with plan, volume, features or capacity.
Mailboxes and hosted SMTP
Services focused on mailboxes with their own operating limits; not necessarily a substitute for a dedicated high-volume engine.
Third-party infrastructure
The application uses the capacity and technical policies of the contracted provider.
Engine deployed at the customer
Software licensed and installed in the customer VPS/Cloud. The company sizes and operates its own delivery infrastructure.
Commercial-model comparison, not a statement of feature equivalence. Third-party pricing and policies should be verified directly with each provider.
TCO
What does a recurring model represent over time?
Under the recurring model, that spend represents approximately
—over the selected period.
Ware Send implementation: R$ 14.999,90. VPS/Cloud, IPs, connectivity, ongoing support and future upgrades follow the contracted commercial scope.
Inside the engine
A delivery platform, not just an SMTP account.
The solution combines authenticated ingress, MIME composition, persistent queueing, signing, transport and diagnostics in a dedicated environment.
REST HTTPS API
Token-authenticated sending with HTML, text, CC/BCC, Reply-To and idempotency. For campaigns, the application can also request an emailed completion summary with a detailed report.
Attachments and inline images
Base64 files and CID images for complete transactional layouts.
Persistent queue
Accepted messages remain in the MTA queue and follow retry policies.
Postfix / MTA
SMTP delivery to recipient MX servers from the customer infrastructure.
DKIM + SPF + DMARC
Domain authentication and alignment configured as part of implementation.
TLS and HTTPS
Secure API ingress and encrypted SMTP negotiation whenever supported during delivery.
Health and readiness
Endpoints and checks for Gateway, MTA, DKIM and queue health.
Production diagnostics
Tools to validate DNS, domain identity, services and operational state.
Implementation validator
Before handover, we test the entire chain.
The project includes technical diagnostics to confirm the main components are behaving as expected. The panel below illustrates the type of validation performed.
infrastructure-check
DNS A
Ready
PTR / reverse DNS
Ready
SPF
Ready
DKIM
Ready
DMARC
Ready
HTTPS certificate
Ready
Gateway/API
Ready
Postfix / queue
Ready
OpenDKIM
Ready
SMTP connectivity
Ready
Integrate your application
After implementation, your system only needs to submit the message.
The application uses the credentials and endpoints delivered with the project. Transport, signing and queueing are handled by the engine.
REST API
Recommended for modern applications, using Bearer authentication and JSON payloads.
Authenticated SMTP
Can be provided according to project scope for legacy systems or applications already configured around SMTP host, port and credentials.
Conceptual REST API sending example
POST /api/v1/sendcurl https://mail.company.tld/api/v1/send \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"from_email": "billing@company.tld",
"to": ["customer@example.com"],
"subject": "Payment confirmed",
"html": "<h1>Confirmed</h1>"
}'
FOR DEVELOPERS · API v1 · SMTP 587/465 · ENGINE 1.0.0+
Open integration documentation
Developer Documentation
HTTP API v1 and SMTP Submission for legacy systems: authentication, payloads, MIME, limits, idempotency and operational status.
Technical transparency
Capacity depends on infrastructure and operational reputation.
Throughput, concurrency and delivery time depend on CPU, memory, network, IPs, domain reputation, recipient policies and environment configuration. High-volume projects require proper sizing, observability and warm-up.
FAQ
What companies usually ask before deployment
Does DB Ware Company send customer emails?
Not as an operational intermediary. Ware Send is deployed in the environment defined by the customer; after handoff, traffic can go directly from that environment to recipient servers.
Does DB Ware Company sell VPS or hosting?
No. Infrastructure is selected and contracted by the customer. DB Ware Company deploys and configures Ware Send in that environment.
How is Ware Send acquired?
As a software and deployment project according to the commercial scope. The engine is installed in the customer environment; support and future upgrades can be contracted separately.
Can I use my own domain?
Yes. Hostname, PTR, SPF, DKIM and DMARC are configured according to the customer identity and project scope.
Is it only for marketing?
No. The primary use case is transactional and operational flows generated by ERP, SaaS, fintech, e-commerce, billing, authentication and other systems.
Is capacity unlimited?
No physical system has infinite capacity. Supported volume depends on infrastructure sizing, IPs, reputation and recipient-server policies.
DBWare
Want to know whether your operation already justifies private email infrastructure?
Share your volume, infrastructure and application scenario. DBWare assesses the required architecture and defines the implementation scope.