Enterprise-shaped. An unreasonable interest in whether it works.Find the point in the portal ↗
what’s the point.

PLATFORM GUIDE

A clearer path
to a controlled web.

Understand the platform, choose your protection layers, and plan a deployment around the way your organization works.

ONE CONNECTED WORKSPACE

Move from activity
to understanding.

Manage web filtering policies, browser profiles, device enrollment, query history, and administrator activity from one console. Use policy diagnostics to understand why a request was allowed or blocked.

The interactive tour is a product experience concept with sample data. It does not operate a live deployment.

PROTECTION LAYER 01

Start at the first request.

DNS filtering controls access at the domain level. Use explicit allow and block rules, maintained blocklists, and encrypted upstream resolution to define which destinations your network can reach.

  • Domain and subdomain control. Apply clear rules across a domain and its descendants.
  • Managed blocklists. Use optional community-maintained feeds and automatic refresh.
  • Explainable decisions. Inspect the local rule responsible for an allow or block.
  • Operational continuity. Caching, upstream failover, and last-good-copy feed retention support day-to-day operation.

DNS works at the domain level. Add browser policies for URL paths and page categories, and managed endpoint controls where stronger network restrictions are needed.

Explore filtering policies ↗

PROTECTION LAYER 02

The useful web,
with clearer boundaries.

Manage URL access and category rules across Chrome, Chromium, and Edge. Apply organization, group, and desktop profile rules in a defined order so the effective policy can be understood.

  • URL and category controls. Match domains, paths, and configurable categories.
  • Browser profiles. Enroll desktops, assign groups, and rotate or revoke profile credentials.
  • Sanitized reading. Offer text-focused reading with checked links and reduced tracking parameters.
  • Native account context. Associate browser profiles with desktop OS account identity.

Managed browser deployment is needed for enforcement. An unpacked extension is removable, and ordinary page inspection is not pre-execution malware isolation.

Explore browser profiles ↗

PROTECTION LAYER 03

Give your policies
some follow-through.

Signed network policy extends control beyond the browser. Specify approved destinations, DNS servers, ports, and interfaces, with verification and enforcement supervision on enrolled devices.

  • Signed policies. Verify policy integrity and protect against rollback.
  • Drift repair. Supervise enforcement and restore the intended firewall rules.
  • Quarantine and restore. Use defined management and recovery workflows.
  • Explicit expiry. Expired policy moves the endpoint into management-only quarantine.

Endpoint policy is a strict destination allowlist. Plan a recovery path before activation. Local administrators can remove controls; native Windows/macOS acceptance is still outstanding.

Review platform readiness ↗

DEPLOYMENT

Your environment.
A deliberate rollout.

The current platform is self-hosted. Your organization operates the management service, controls local data, and decides how DNS, browser profiles, and endpoint policies are deployed.

Evaluate

Explore the interface, map your filtering requirements, and review release boundaries.

Start with the interactive tour.

Pilot

Validate policies in a controlled environment and confirm your recovery procedures.

Prove the behavior on your devices.

Roll out

Enroll browsers and endpoints deliberately, with acceptance criteria for your environment.

Expand when your tests support it.

Operate

Review activity, keep policies current, and manage local retention and backups.

Keep the operational context close.

Engineering installation instructions are available in the technical deployment guide. Team support, managed services, and enterprise rollout assistance are still in development.

Find your starting point.