Customer infrastructure
Deploy in the network, region, and compute environment approved by your security team.
System-sovereign deployment
Keep company AI inside your boundary.
Run Friday, customer storage, the approved open model, and permissioned agents inside infrastructure you control. The Friday vendor receives and retains no company artifacts.
Your systemYour modelYour retention policy
Sources
Friday
Open model
0company artifacts0model prompts0generated outputs
What system sovereign means
The whole intelligence loop stays with you.
Application, normalized sources, inference, briefs, and agent execution remain inside the customer environment. Your instance retains what your policy requires; the vendor does not receive it.
Customer storage
Keep source artifacts, briefs, history, and audit records in stores governed by your policy.
Open-model runtime
Run an approved model locally without sending prompts to an external model API.
Controlled integrations
Authorize only the source scopes and agent actions required by the selected workflow.
From source to accountable action
Every transition remains inside the boundary.
The same customer-controlled environment reads, normalizes, reasons, acts, and preserves the evidence trail.
- 01Read
Retrieve authorized activity from the company tools selected for the workflow.
- 02Normalize
Convert artifacts into one searchable source model inside the boundary.
- 03Reason
Synthesize briefs and evaluate workflow evidence with the local model runtime.
- 04Act
Run only allowed agent actions, pausing for human approval where required.
- 05Audit
Keep source, sync, decision, and agent events available to administrators.
Shared responsibility, written down
Infrastructure ownership stays explicit.
Personalized onboarding records who owns identity, storage, models, backups, upgrades, observability, and incident response.
LayerCustomerFriday
InfrastructureConfigures and operatesDeployment guidance
Data & retentionControls policy and storageNo vendor retention
Model runtimeApproves and operatesRouting and eval design
Agent actionsAuthorizes boundariesPermissioned workflow
Zero vendor retention is a boundary, not a missing policy.
Your own Friday instance still retains search, history, and audit data according to the policy you control.
How deployment is scoped
Map the boundary before the first workload.
Environment
Network, region, compute, storage, and backup ownership
Identity
Workspace roles, source authorization, and administrative access
Model policy
Approved model, runtime, routing, and observability requirements
Operations
Upgrade process, audit export, retention, and incident ownership
Deployment working session · 15 minutes
Bring your architecture. Leave with a sovereign deployment map.
We will map the environment, storage, model policy, operating ownership, and the first permissioned workflow inside that boundary.
Start personalized onboarding Built around your workflow, not a generic tour
- 01Verified bottleneck
- 02Sovereign deployment
- 03Permissioned agent