Manage your organization's AI use
in one place
MiWork Gate applies budgets, permissions and personal data policies where coding tools, AI agents and internal apps call AI models. Review cache savings and usage directly in the web console.
More AI tools. Fragmented governance.
Route model requests through one gateway to apply consistent access rules and logging.
Key features
Need to review policies and a configuration for your organization? Talk to our team →
See your AI savings,
not just your spend
When a previous response can be reused, no model call is made, no charge is incurred and the budget is unchanged. Savings accumulate in the console.
- —Compare savings and cached responses by period and model
- —Savings use the actual cost of the original response
- —Cached responses are encrypted and not shared across users
Generative AI usage security —
personal data policies and team model access
Connect internal LLMs through the same gateway as external models. Choose allowed models by team according to security and cost requirements.
- —Restrict teams handling sensitive data to internal LLMs
- —Use internal LLMs for everyday work and external models for demanding tasks
- —Set allowed models only within higher-level permissions
Before a request reaches the model
Requests blocked by policy or completed without usage are not charged. Requests whose usage cannot be fully verified are kept for review rather than recorded as zero-cost.
An admin console scoped to your role
Admin console
Manage operations, requests, budgets, models, pricing, policies and audit logs in one web console. Use local accounts or Microsoft Entra ID for login.
Signing in does not grant administration rights. Viewing prompt bodies requires separate authorization, independent of role.
Common use cases
- Consistent governance across internal AI toolsManage tool permissions and policies in one place.
- Report AI cost savingsReview cache savings and model costs by period.
- Allocate AI costs by departmentUse organization and team budgets with model-level costs and charges.
- Work involving sensitive informationLimit the team to internal LLMs and mask or block personal data.
Deployment and operations
- —Install and operate on your organization's servers
- —Separate model request handling from administration
- —Operate a separate Gate instance for each integrated application
- —Encrypt model access keys, stored prompts and cached responses
- —Keep cost records intact and track corrections separately
We recommend restricting administration to internal networks. The detailed configuration is determined after reviewing your deployment environment.
Frequently asked questions
Which AI models can I connect?+
Connect OpenAI and Anthropic models, OpenAI-compatible models such as DeepSeek, GLM and Qwen, and internal LLMs. Some features, such as provider-side paid search tools, are not supported. Confirm the models and features you plan to use in your environment.
What happens when a budget is exceeded?+
Remaining budget is checked before forwarding. Requests that cannot be covered are rejected without reaching the model. Conservative cost estimates mean even short requests may be rejected when little budget remains. Cached responses cost nothing and may still be returned after the budget is exhausted.
Can it filter out all personal data?+
Pattern-based checks cannot guarantee detection of all personal data or attacks. Uninspectable content such as images and files is forwarded and logged by default; enabling stricter inspection blocks such requests. Model responses are passed through unchanged.
Are prompt contents stored?+
Not by default. If body storage is enabled, personal data and secrets are removed before encrypted storage and deletion after the configured period. Usage and cost logs are separate. Response caching stores encrypted model responses for a set time, not the original request text.
Where can I see cache savings?+
The console's operations view shows savings, cached response counts and provider cost savings by period. The model cost table shows cached responses and savings per model. Savings depend on how many requests can reuse a response in your workflow.
Which requests can use the cache?+
The same user can reuse a response within its retention period for an identical request using the same model and options. This is not similarity-based search. Requests with files, images or continued conversations are not cached. You can bypass the cache when a fresh answer is needed.
Can I connect an internally operated LLM?+
Yes. Register internal LLM servers supporting OpenAI or Anthropic request formats alongside external models. Administrators predefine allowed server addresses. Gate does not automatically change models based on request content; team model permissions control the available scope.
What happens if an AI provider fails?+
By default, a request is sent once. If an administrator enables failover for the model, a connection failure triggers a retry through another connection. No switch occurs once response delivery begins. Retry billing rules are explained during deployment planning.
Lower AI costs. Establish clear governance.
Tell us about your AI tools, models and internal LLMs. We will review a MiWork Gate configuration that fits your organization.