How your private AI deployment works
From first call to a live, branded AI assistant in about two weeks. Here is the full walkthrough, including where your data lives at every step.
The architecture in one picture
Three zones. Your data only ever lives in the first two, and the second one belongs to you.
Zone 1: Your systems
Where your data already lives
- SharePoint and OneDrive
- Google Drive and Gmail
- CRM and sales tools
- Accounting and payroll
- File shares and internal docs
Zone 2: Your private environment
Dedicated Azure deployment
- Branded chat interface on your domain
- Document index and retrieval
- Memory across projects and clients
- Role based access and audit logs
- Workflow automations
Zone 3: AI models
Zero retention API calls
- Claude, GPT, Gemini and 30+ models
- Enterprise API agreements
- No prompt storage
- No training on your data
- Swappable at any time
The two week deployment timeline
Week 1, Days 1 to 2
Discovery and data mapping
We meet with you for one working session. You tell us how your business runs, which documents and systems matter, and who should have access to what. We come out of that call with a data map: every source we will connect, every permission boundary we will enforce, and the workflows your team repeats every week.
Week 1, Days 3 to 5
Environment provisioning
We provision a dedicated Microsoft Azure environment for your company. This is your infrastructure, not a shared tenant. We configure networking, encryption, authentication with your existing logins, and role based access. Nothing about this step requires your IT staff.
Week 2, Days 1 to 3
Data connection and indexing
We connect your approved sources: SharePoint, Google Drive, file shares, CRM records, accounting exports, and any internal documents you designate. Documents are indexed inside your environment so the assistant can answer questions with sources. Your originals never leave your control.
Week 2, Days 4 to 5
Branding, training, and launch
We apply your logo and colors, put the assistant on your domain, and run a live onboarding session with your team. Every employee leaves that session knowing how to ask questions, generate drafts, and run workflows. Then you are live.
What actually happens to your data
This is the part most vendors hand wave. We would rather spell it out.
Your documents stay in your environment
Files are indexed and stored inside your dedicated Azure deployment. When the assistant answers a question about a contract, the contract itself is retrieved from your environment, not from a model's memory.
Model calls carry zero retention
When your team chats, the relevant snippets are sent to the model through enterprise API agreements with zero data retention. The provider processes the request, returns the answer, and keeps nothing. Your prompts never become training data.
Access mirrors your org chart
Role based access means the assistant only answers from documents each user is allowed to see. Your bookkeeper's AI does not see HR files. Your intern's AI does not see the P&L. Audit trails record who asked what.
You can leave anytime
It is your environment and your data. If you ever walk away, your documents and history are yours to take. There is no lock in by hostage taking. We keep clients by being useful.
Want the security detail? Read the full security and data privacy overview or see per seat pricing for private GPT deployments.
See a live deployment on your screen
Book a 30 minute demo and we will walk you through a real private environment, then map the two week timeline to your company. Or email shawn@hummingagent.ai with questions.