Hosted Safe Zone
Start in minutes
Use the managed portal while your team proves the workflow and gathers deployment requirements.
Open hosted Safe Zone Deployment room / 01
Put the boundary where your trust lives.
This is not a download button for another desktop app. It is the handoff point between a hosted proof of concept and a RedactNode deployment your IT team can own.
Organisation-owned runtimeShort-lived token mappingsHash-only audit evidenceNo raw prompt in IT feedback
deployment boundarydecision required
your organisation
portal
proxy
audit
Raw PII stops here
outside providermasked request only
Choose the boundary
Three ways to make the next step real.
There is no universal “download” for a privacy deployment. Start with the boundary your organisation can actually operate.
Private deployment
Bring the boundary inside
Run the portal, proxy, Redis, Postgres, and audit controls in infrastructure your organisation operates.
Request a private buildRestricted network
For the rooms without exits
For sensitive environments, discuss an installation path designed around restricted egress and internal operations.
Talk to deployment teamInside the boundary
A small control plane. A clear line.
The private build is designed to be understandable: one protected portal, one masking gateway, temporary state, and an audit trail that records evidence without storing the secret.
See the gateway architectureSafe Zone Portal
The employee-facing chat surface
Tanda Proxy
Mask → forward → restore
Audit controls
Hash-only evidence and review
Redis · Postgres · your network boundary
Choose your path
Where should RedactNode run?
Start with the boundary you can operate today. You can move from hosted to private deployment as requirements become clear.
Recommended path
Your infrastructure, without your hardware
Run the protected portal and gateway in an organisation-owned cloud account with a clear operating boundary.
Portal, Proxy, Redis, Postgres, audit controls
Request architecture reviewDeployment pack
No mystery box after the call.
A private deployment starts with an operating plan, not a binary. We prepare the material your platform, security, and data teams need to review the rollout.
Architecture and data-flow diagram
Environment variable checklist
Network and provider requirements
Redis and Postgres setup notes
Chrome extension pilot guide
Audit and retention configuration
The sensible rollout
Prove the workflow before you move the walls.
Start with hosted Safe Zone, run a small pilot, then move the boundary when ownership, network, and retention requirements are clear.