Skip to content

Subprocessors

Name the provider and the role it performs.

Netrix relies on infrastructure and customer-configured services with different data roles. The deployed configuration uses a VPS and Cloudflare for application delivery, PostgreSQL for application records, object storage for files, Mailgun for email, Screaming Frog for crawling, Anthropic for account-enabled AI, and local-search providers when customers connect them.

Request access Explore the platform
ControlSystemHumanClient
Collect evidence✓——
Review meaning—✓✓
Approve action—✓✓
Verify output✓✓—
The exact permission depends on account role, site ownership, connector capability, and the requested action.

What the workflow must answer

Keep the operating question attached to the evidence.

01

Core application delivery

Hosting, DNS and edge protection, database, object storage, and transactional email support the Netrix service.

02

Feature processors

Crawl, AI, and local-search providers process the bounded tasks or data the configured feature requires.

03

Customer-owned connections

Some provider accounts and credentials belong to the customer and are used only after explicit configuration.

Control review

Translate the promise into something an operator can inspect.

Review the trust center
01Core application delivery
Hosting, DNS and edge protection, database, object storage, and transactional email support the Netrix service.
02Feature processors
Crawl, AI, and local-search providers process the bounded tasks or data the configured feature requires.
03Customer-owned connections
Some provider accounts and credentials belong to the customer and are used only after explicit configuration.

An accountable trail

A useful state says exactly what happened.

  1. 01Observed

    The source evidence is recorded.

  2. 02Interpreted

    The condition is reviewed in context.

  3. 03Decided

    An authorized person chooses the next state.

  4. 04Applied

    A supported destination accepts the action.

  5. 05Verified

    The public result is read independently.

  6. 06Reported

    The claim matches the available evidence.

Product truth

Automation prepares work. Authority stays visible.

  1. 01
    No hidden autopilot

    Netrix does not publish AI drafts or apply SEO changes without an explicit authorized action.

  2. 02
    No optimistic verification

    An accepted write and a confirmed public value remain different states, and an unreadable page stays unknown.

  3. 03
    No invented scope

    Pages describe the product’s current boundary and name external providers or unfinished paths where they matter.

Continue the work

Related Netrix resources

Browse all resources

Security

Put a concrete control at every place authority enters.

Review Netrix tenant isolation, credential handling, network protections, connector authentication, deployment gates, and operational controls.

Data protection

Data protection begins with knowing which system holds each record.

Understand what Netrix stores, how tenant data and credentials are separated, transport protections, logs, and deletion boundaries.

Retention

State what expires, what persists, and what still requires an operator.

Review current retention, report expiry, crawl payload, audit history, logs, connector teardown, and account deletion behavior.

See it in your workflow

Bring the evidence, decisions, and outcomes into one trail.

Request access