Subprocessors
See which providers help run Netrix and what each one does.
Netrix uses outside infrastructure and customer-connected services for different jobs. The current production setup includes hosting and Cloudflare delivery, PostgreSQL, object storage, Mailgun, Screaming Frog, Anthropic when AI is enabled, and local search providers when a customer connects one.
What to look for
Get the answer without losing sight of where it came from.
Providers that keep the application running
Hosting, DNS and edge protection, database, object storage, and transactional email support the service.
Providers behind specific features
Crawling, AI, and local search services process the data needed for the feature a customer chooses to use.
Connections the customer owns
Some provider accounts and credentials belong to the customer and are used only after the account connects them.
How Netrix handles it
Look past the promise and see what the product actually does.
- 01Providers that keep the application running
- Hosting, DNS and edge protection, database, object storage, and transactional email support the service.
- 02Providers behind specific features
- Crawling, AI, and local search services process the data needed for the feature a customer chooses to use.
- 03Connections the customer owns
- Some provider accounts and credentials belong to the customer and are used only after the account connects them.
From finding to follow-up
See where the work stands—and what still needs to happen.
- 01Found
Netrix records the page and the issue it found.
- 02Reviewed
Someone checks the finding in context.
- 03Approved
The right person chooses what should change.
- 04Applied
A supported connection accepts the change.
- 05Checked
Netrix reads the public page again.
- 06Shared
The report summarizes the audit and fixes currently marked applied.
A few things worth knowing
Netrix can prepare the work. Your team still makes the call.
- 01Nothing publishes itself
AI drafts and supported SEO changes wait for an authorized person to act.
- 02A write is not proof
Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.
- 03Limits belong in the open
When a feature depends on another provider or stops short of a complete workflow, the page should say so.
Keep exploring
More on this part of the work
Security
Security starts with limiting who can reach an account, a credential, or a live site.
Learn how Netrix separates accounts, protects credentials, authenticates connections, gates site changes, and secures production traffic.
Data protection
To protect data well, you first need to know where it lives.
See what Netrix stores, how account data and credentials are separated, how traffic is protected, and what deletion does not reach.
Retention
Some records expire automatically. Others remain until the account or an operator removes them.
Review how long reports, audit history, crawl files, logs, and connection records remain, and what account deletion removes.
See how it fits your team