Model providers
Customer model keys are used by default, so model access remains tied to the provider account the customer controls.
Developers · Hosting
Know what Deixic hosts and what stays under customer control.
Deixic is a hosted service. The application and application data run on Google Cloud Platform; Cloudflare provides DNS, TLS, and traffic proxying.
Credentials
Bring model keys by default and limit each connection.
Connected systems
Connector profiles and tools can be scoped by team or person and inherit the permissions granted at the provider.
Credential references
Tool-call records point to credential references rather than exposing secrets in the action history.
Credential operations
Connection health is visible, and managed credentials can be rotated or revoked from Deixic.
Data agreements
Set retention and confirm residency during procurement.
Retention is defined in the enterprise agreement. Data residency is confirmed during procurement; Deixic does not publish a universal default residency commitment. The DPA and subprocessor list describe the contractual and processing boundaries.
Production rollout
Start with one connected action and its real approval owner.
- 01Choose one consequential production tool call and identify its target system.
- 02Connect the provider with only the permissions that action needs.
- 03Define the allow, deny, or approval rule and name the decision owner.
- 04Run the path and verify the request, decision, cost, and result in activity history.
- 05Add the next action, connected system, agent, or business unit after the first path is operating.
Continue the security review.
Review the procurement path, trust controls, and service status.