Bring AI to your data. Not your data to AI.
Build and operate AI inside infrastructure you control — from private cloud environments to fully on-premise deployments.
Margins designs private AI systems around your data, existing technology and operational requirements, using the right combination of open-source, privately deployed and external models for each workload.
Your infrastructure. Your data. Your intelligence.
Your most valuable AI will know your business.
The more useful AI becomes, the more proprietary context it needs. Generic AI knows the world. Enterprise AI needs to understand your company.
That context is what makes enterprise AI useful. It is also what makes architecture increasingly important.
- 01Your customers.
- 02Your products.
- 03Your contracts.
- 04Your operational history.
- 05Your documents.
- 06Your processes.
- 07Your internal terminology.
- 08Your decisions.
- 09The knowledge accumulated by your people.
The question isn’t only what AI can do. It’s what information it needs access to in order to do it.
Control the architecture, not just the application.
“Private AI” can mean different things. For us, the important question is where each component operates and where information is allowed to move.
Private AI isn’t about isolating everything. It’s about deciding intentionally what stays inside, what can leave, and why.
- 01Customer-controlled infrastructureThe core system operates within infrastructure controlled by your organization.
- 02Private modelsModels can run inside your cloud or on-premise environment.
- 03Open-source modelsModels can be deployed and operated without routing every request through a public AI service.
- 04Private enterprise knowledgeRAG and knowledge systems operate against information stored inside your controlled environment.
- 05Selective external AIApproved external models can still be used where their capabilities justify it and the data boundaries allow it.
Private isn’t one architecture.
Customer cloud
AI inside your existing cloud environment.
Applications, data and AI infrastructure operate within your organization’s cloud accounts.
Best fit · Strong control without operating physical infrastructure.Private cloud
Dedicated AI infrastructure.
AI workloads run within isolated cloud infrastructure designed around your requirements.
Best fit · Stronger separation or dedicated compute.On-premise
AI inside your own infrastructure.
Models, data and applications run locally without core workloads leaving your environment.
Best fit · Operational, data, connectivity or organizational requirements demand local control.Hybrid
Keep sensitive workloads private. Use external AI selectively.
Different workloads use different models and environments depending on sensitivity, performance, capability and economics.
Best fit · For many enterprises, the most practical architecture.The goal isn’t maximum isolation. It’s the right level of control.
Use the best model for the job — within the boundaries of the business.
A production AI system doesn’t have to depend on one model. A simple internal classification task may not need the world’s most capable model. A complex reasoning task might. A sensitive document workflow may need to remain entirely private. A computer vision problem may need a specialized model rather than an LLM at all.
Model selection should be an architectural decision, not a company-wide default.
Powerful AI doesn’t have to mean a public API.
Modern open and deployable models make it possible to run increasingly capable AI within customer-controlled environments — creating new options for enterprises that need greater control over:
It introduces its own requirements around infrastructure, evaluation, optimization, monitoring and ongoing operations. Margins helps determine when private deployment creates enough value to justify that complexity.
Your data stays close to the systems that created it.
Your company already has years of intelligence inside ERP systems, CRM platforms, databases, document repositories, email, contracts, data warehouses, internal applications — and the knowledge of your employees. Instead of moving all of that into a new AI platform, we design the AI layer around the existing enterprise environment.
AI becomes another capability inside the enterprise architecture — not another silo beside it.
Build AI around what your company knows.
Give people access to organizational knowledge without exposing it unnecessarily outside the business. Retrieval and enterprise knowledge architectures let AI work against relevant company information while respecting the boundaries designed around the system.
- Documents
- Policies
- Procedures
- Technical documentation
- Customer history
- Product information
- Contracts
- Internal research
- Operational knowledge
- Subject-matter expertise
Generic AI knows what everyone knows. Your advantage comes from what only your organization knows.
Turn what your people know into intelligence your company owns.
Some of the most valuable information in an enterprise isn’t in a database. It’s inside people’s heads. Capta captures that expertise and turns it into structured organizational knowledge that can become part of your private AI environment.
Explore CaptaGive AI access to your business without giving it access to everything.
An enterprise agent might need to read a customer record, retrieve a document, analyze an order, prepare an ERP update, generate a report or trigger a workflow. It shouldn’t automatically gain unrestricted access to every connected system.
- →Read a customer record.
- →Retrieve a document.
- →Analyze an order.
- →Prepare an ERP update.
- →Generate a report.
- →Trigger a workflow.
- 01Identity
Who is requesting the action?
- 02Permissions
What information can this user or agent access?
- 03Tools
Which systems can the agent interact with?
- 04Actions
What is it allowed to do?
- 05Approval
Which actions require a person?
- 06Auditability
What happened and why?
The more AI can do, the more precisely we need to define what it is allowed to do.
Run AI where your business requires it.
Margins can engineer AI systems where models, applications and data processing operate within customer-controlled local infrastructure.
Potential workloads- Data sensitivity.
- Internal architecture.
- Connectivity.
- Latency.
- Operational resilience.
- Existing infrastructure.
- Organizational policy.
- Requirements specific to the industry or use case.
Cloud AI is an option. Not a prerequisite.
Sometimes the best place to run AI is where the work happens.
Computer vision, industrial systems, field operations and environments with unreliable connectivity can benefit from processing closer to the source — reducing latency, improving resilience and limiting unnecessary data movement.
- Local servers
- Industrial computers
- Edge devices
- Workstations
- Embedded systems
Both ends of the architecture spectrum, in production.
Predictive AI without business data leaving the company.
A system built around four years of invoice history identifies customers showing early signs of revenue decline. It operates inside the customer’s ERP environment — no cloud, and no data leaving the company.
Enterprise AI inside the customer’s own cloud.
An AI mobile cockpit combining purchasing patterns, machine-learning detection, customer briefings, spoken reporting and an AI assistant — running inside CIAK’s own cloud, with no business data leaving that environment.
See the outcome →Private AI still needs to be operated.
Running AI inside your environment doesn’t remove the operational requirements. Models still need monitoring. Workflows still fail. Costs still matter. Quality can change. So private AI needs operational visibility just as much as cloud AI.
Control without visibility isn’t control.
- Model performance
- Workflow execution
- Infrastructure
- Latency
- Failures
- AI quality
- Usage
- Cost
- Human intervention
- Business outcomes
An operational layer for enterprise AI.
Rivermind is Margins’ proprietary AI Operations Platform — an orchestration and operational control layer across models, data, tools, business rules and AI workflows. In a private architecture, it sits between enterprise systems and the AI capabilities operating around them.
Explore Rivermind (opens in a new tab)More control comes with different economics.
Private AI shouldn’t be sold as automatically cheaper.
Low-volume workloads and complex reasoning tasks.
Usage is high, workloads are predictable, specialized models are sufficient, or infrastructure control creates additional value.
- Usage volume
- Model size
- Compute requirements
- Latency
- Availability
- Infrastructure
- Licensing
- Engineering effort
- Operations
- External API costs
We evaluate private AI as a business architecture decision — not an ideological one.
Design the boundary first.
Privacy is an architecture decision, not a deployment checkbox.
- 01
Understand
Identify the use case, business outcome and information involved.
- 02
Classify
Understand data sensitivity, access requirements and operational constraints.
- 03
Architect
Determine what should run locally, privately or through approved external services.
- 04
Evaluate
Test candidate models against quality, performance, infrastructure and economics.
- 05
Engineer
Build the complete AI, software, data and integration system.
- 06
Deploy
Move the system into the target customer environment.
- 07
Operate
Monitor performance, reliability, quality and infrastructure.
- 08
Improve
Continuously optimize models, workflows and economics based on production behaviour.
Private AI may be the right approach when…
If a hosted model provides the right capability within acceptable data boundaries, we may recommend using it.
- Your AI needs access to highly valuable proprietary information.
- You want greater control over where information is processed.
- AI needs deep access to internal enterprise systems.
- Your workloads justify dedicated infrastructure.
- You need AI to operate without continuous external connectivity.
- You want flexibility across different model providers.
- You want to deploy open-source models internally.
- You want organizational knowledge to remain inside controlled infrastructure.
- Your existing technology or policies require local deployment.
For many enterprises, the answer won’t be public or private. It will be both — deliberately.
Architectural tendencies, not universal truths.
Private AI requires more than model expertise.
Running AI inside enterprise environments requires capability across the entire stack.
AI & ML Engineering
Evaluate, deploy and optimize the right models.
Software Engineering
Build the applications and workflows around them.
Data Engineering
Connect proprietary enterprise information.
Enterprise Integration
Work with ERP, CRM and internal systems.
Infrastructure
Deploy into customer-controlled environments.
Forward Deployed Engineering
Adapt the system as it meets operational reality.
Managed AI
Operate and improve it after deployment.
Related capabilities
Enterprise Knowledge & RAG
Build AI around your proprietary company knowledge.
Explore Enterprise Knowledge →AI Engineering
Engineer production AI around your systems and operations.
Explore AI Engineering →Security & Trust
See how we approach architecture, data boundaries and enterprise control.
Explore Security & Trust →Managed AI
Operate and monitor private AI after it enters production.
Explore Managed AI →
Keep the intelligence that makes your business valuable under your control.
We’ll help determine what should run privately, what can use external AI, which models fit the workload, and how to engineer the complete system around your existing technology.
Discuss your architectureBring AI to your data. Not your data to AI.