Questions people ask, before they ask the serious ones.

What is the difference between the open-source engine and the commercial service?

The engine is a local classifier you run yourself. The service is a private-deployment gateway that sits between your ingest and your infrastructure, with a verified buffer, a chain-of-custody break, multimodal coverage, operational support, and a contract. They solve adjacent problems.

The service is not a scaled-up version of the engine, and the engine is not a diminished version of the service. If you want a tool you own and operate, the engine is the right answer. If you want infrastructure someone else operates so your corporate environment never touches the raw stream, the service is the right answer.

Does the service store our users' content?

No. The gateway filters ingest before persistence. Only the bleached stream and the audit trail cross the boundary into your environment, and the gateway does not itself retain raw material beyond what classification requires in-flight.

What modalities does the service cover?

Image, video, and audio. Audio handling includes transcription so policy can be applied to spoken content, not just the waveform. The open-source engine covers image and video.

Can we self-host the service?

No. Self-hosting is the engine. The service is the service because we operate it; the operational surface, the buffer, the chain-of-custody break, and the SLA are the product. If we handed you the binary you would have a classifier, not a gateway.

What is the licence on the open-source engine?

Apache-2.0. Full commercial use permitted. Fork it, ship it, run it in your products.

Why are there two domains?

SFWaaS and NSFWaaS are the polite and the blunt names for the same detection surface. Both domains point at this site; SFWaaS.com is canonical. Pick whichever name you prefer to say out loud.

Why is the pricing page missing?

Because this is not a SaaS product. It is a private infrastructure engagement. Pricing is a function of throughput, modality coverage, trust-policy complexity, deployment topology, and operational support level. We will quote after a conversation, not before.

Why is the name… like that?

Because it is exactly what the engine does. We named it on purpose. If you get the reference, we have already agreed on something.

Is this a Creative Mayhem product?

Yes. Creative Mayhem UG, Berlin. We also operate rAIdio.bot, Doomscroll.FM, provcheck, Sortalizer, and a handful of other local-first tools. SFWaaS is the infrastructure layer we built for our own products first; we offer it to others because the demand turned out to be real.

How do we engage?

Email [email protected]. Include who you are, what you run, roughly what you need a gateway for, and a jurisdiction. We will reply.