More than a name: operational discipline
The Pitbull name is intentional. The historical role of pit bull terriers — isolating a threat that broke from the pack while protecting the main structure — mirrors our architecture: isolate the bad sender before they collapse the entire IP block, keep operations running.
In 2019 we watched hosting providers land on RBLs because outbound spam leaked from shared servers. That day we asked: Why is mail security separate from delivery, quarantine separate from reporting? The answer became Pitbull Secure Gateway — inbound gateway, outbound relay, quarantine, NOC, firewall, audit and customer portal on one operations surface.
What we do — and what we don't
We do: Rspamd, ClamAV/Avast REST, policy engine, quarantine, live NOC, outbound reputation management and multi-tenant hosting operations on the SMTP hot path.
We don't: "AI solves everything automatically" marketing. Our radar screens run observe-only by default; automatic ban, reject or quarantine activates only when you define explicit policy. We respect mail flow — because every false positive is a customer's real transaction.
Where we operate
Production infrastructure runs at Kuzey Data Center Tier III in Çekmeköy, Istanbul. Email metadata and operational logs are processed within Turkey; data residency and log separation are part of the architecture for KVKK and enterprise audit requirements.
Who we work with
- Hosting & ISP: Shared IP outbound abuse, tenant isolation, WHMCS billing
- Enterprise IT: BEC, phishing, M365 hybrid, compliance reporting
- Banks & Finance: SWIFT notifications, audit log, outbound reputation
- Universities: Student mail scale, campaign-based phishing protection
- MSP & Reseller: Multi-tenant portal, executive PDF customer reports
Engineering principles
- The hot path is sacred. Heavy analysis does not slow mail acceptance; target <200ms filter latency.
- Visibility is default. Every reject decision shows SPF, DKIM, DMARC, Rspamd symbol and score breakdown.
- Sensitive data is not logged. Passwords, API keys and tokens are never written to audit log; masking is mandatory.
- Delivery does not come after security. Provider Transport Pool Auto Balancer and Blacklist Smart Retry Engine are part of delivery intelligence.
Measured by operations, not stickers
We don't paste a 99.9% spam blocking sticker. Instead we measure queue depth, Microsoft defer rates and per-tenant abuse signals on NOC screens. Our customers want a clean delivery report at dawn — not an abuse ticket — and we built the platform for that.
