Content moderation as infrastructure
Your platform should not have to touch what your users upload. We handle the raw data. You handle the business. The private buffer between user content and your corporate environment.
SFWaaS is a private-deployment moderation gateway. Your ingest stream routes through a verified buffer that filters prohibited material before it reaches your infrastructure. Your systems never possess the raw content. Your logs never store it.
Private deployment.·No public endpoints.·Serious inquiries only.
What it does for you
Three outcomes your risk team will recognise.
You never held it.
The raw ingest stream terminates at the gateway, not inside your environment. Your corporate estate never takes possession of prohibited material, which is the only way deniability is actually defensible.
Nothing public to attack.
No public endpoints on your side. No ingress your security team has to monitor. No master library for anyone to scrape or enumerate. The architecture of the gateway is itself a control.
Your policy, your audit trail.
Trust policy defined by you, not us. Throughput and latency to contract. Operational support and audit logging on the service, not on a shared cloud product whose SLA moves when it suits them.
The architecture
Your stack does not see what it does not need to see.
Between your ingest path and your infrastructure sits a cryptographically verified buffer. Raw material is filtered, classified, and bleached before a single byte crosses to your side.
What reaches your systems is a clean stream and an audit trail. What does not reach your systems is everything else, and that is the point.
The gateway operates out-of-band from your environment. There is no shared tenancy with other customers, no public admin surface, no exposed control plane. The chain of custody breaks at the buffer. Your security team audits the stream they receive; they do not audit what never touched them.
Deployment topology, trust-policy schema, and operational details are discussed under NDA. Inquiries: [email protected].
There is also an engine
We open-sourced the classifier core.
The SFWaaS gateway is a service. The classification engine inside it is a tool, and we shipped a version of it under Apache-2.0 so you can understand the primitives we operate on, and so the community working on content safety has a real reference implementation to build from. The engine is not a diminished version of the service. The service is not a scaled-up version of the engine. They are different products.
Hotdog / Not Hotdog
The open-source classifier engine. CLIP-based. Self-hosted. Apache-2.0. Named deliberately.
Engage
Commercial inquiries are private by default.
There is no web form. There is no intake questionnaire. There is no free trial, public pricing page, or self-serve portal. Reach out when you are serious and we will take it from there.