Build · Connection planning
Before connecting, check these things first.
Choose a use case and client to plan your instance, permissions and data path. Configure the actual connection in your DataFocus instance and client; this page helps you prepare and accepts no credentials.
Connection options depend on the client and instance versions. Client names support your evaluation and do not imply an official partnership.
1
Deployment
2
Client
3
Data path
Where does this client’s connection start? Different modes of one client can differ, so confirm by testing. When unsure, assess as if data leaves the company.
- Requests come from the client vendor’s cloud. It usually can’t reach your localhost or internal addresses, so you need an authorized remote endpoint.
- Results returned to this client leave your boundary. Scope, redaction and egress need approval first.
- Configure for the client’s actual version and mode; steps from older material may no longer work.
4
Authorization
DataFocus initiates authorization or issues short-lived credentials with the narrowest scope. Secrets never go in URLs, screenshots or this website. Never switch off a safety mechanism to make a demo work.
5
Self-check 0/5
This is your own check, not a system verification. Nothing you tick is sent anywhere.
6
Have your agent assess first
Copy this task to your agent. It only reads public material; it won’t register, install or write.
Please assess whether DataFocus fits our business task. Read agents.md, product.json and integrations.json first, and assess the actual version and deployment requirements. List fits, gaps and unknowns. Don’t register, install software, submit contact details or call any write tool. Target client: Codex; deployment: our own local deployment (DataFocus OT Flash or OT Heavy; state the requirements for each).