Sitr for Institutions · schools · masajid · ISPs · fleets
A filtering policy you can defend with documents,
not assurances.
When parents, boards or subscribers ask what your filter does with browsing data, “the vendor says it’s fine” is a weak answer. “Here is the public architecture, the empty endpoints table, and the checksums — verify them” is a strong one. That’s what you deploy with Sitr.
Who deploys Sitr
The product is the same auditable filter families install at home. What institutions buy is everything around it: deployment, support, licensing and someone accountable on the phone.
Islamic schools & madaris
Deploy Sitr across labs, library machines and take-home devices via your MDM. Students get filtering that provably doesn’t log them — a policy you can defend to parents with documents, not assurances.
Masajid & community centers
Public Wi-Fi and shared computers stay clean without routing your congregation’s traffic through a third-party logger. Set it up once; the fail-visible badge tells volunteers at a glance that protection is on.
Halal ISPs & network operators
Offer family filtering as a differentiator without becoming a surveillance vendor. License the maintained, appeals-backed blocklist feed and ship “powered by Sitr” — the brand your subscribers can audit.
Fleets & managed devices
Enterprise policy templates for Chrome/Edge, deployment runbooks, and a support contract with real humans. Your IT team gets configuration authority; your users still get the empty endpoints table.
What's on offer
The code is MPL-2.0 and free at any scale — you could deploy tomorrow without talking to us. These are the things forks can't give you.
Plans, plainly
// Both tiers include the support SLA; deployment help, blocklist feed and white-label licenses priced separately. Device counts are contractual — self-declared at signup, trued up at renewal. We can't meter them: your deployment never touches our servers, and that's the product. Billed annually — subscribe online above, or by invoice (bank transfer) on request.
Deployment — one policy push, not fifty installs
Nobody walks desk to desk. Sitr deploys through the browser's own enterprise machinery, from whatever management console you already run.
Force-install fleet-wide
One ExtensionInstallForcelist policy entry installs Sitr on every managed Chrome or Edge browser — pushed from Google Admin Console, Microsoft Intune, Jamf, SCCM, or plain Group Policy. Uninstall is blocked by the same policy.
Configure centrally
The extension reads managed-storage policy with a published schema, so the console that installs it also configures it: category settings and organization defaults land as policy JSON. IT holds configuration authority; users can't override it.
Nothing phones home
Deployment at scale adds no servers and no reporting: filtering stays on-device on every seat, and your deployment never touches our infrastructure. Rollout runbooks and policy templates come with the deployment-support contract.
Why an institution can sign this
Your diligence is already done, in public: the threat model, data-flow inventory and inclusion policy are documents you can attach to a board proposal today.
And because filtering is on-device, adopting Sitr never puts you in the position of operating — or answering for — a log of your students', congregants' or subscribers' browsing.
Blocklist disputes don't route through your front office. Anyone affected can use the public appeals process directly, and every decision is reviewed against published criteria — governance you inherit instead of invent.
[email protected] · tell us who you serve and on what platforms — we'll reply with a deployment sketch and a quote.