More input types create more paths
Normalize text, images, files, tools, and associated metadata so policy stages can make consistent decisions.
Google Gemini integration
Entrovik's native Gemini adapter translates messages, system instructions, tools, function calls, embeddings, model responses, and usage without pushing provider-specific logic into policy packages.
Why teams act
Entrovik gives security, platform, compliance, and application teams a shared technical boundary without coupling enterprise policy to one provider SDK.
Normalize text, images, files, tools, and associated metadata so policy stages can make consistent decisions.
Apply model policy and cost configuration independently of hard-coded pricing or application allowlists.
Apply request policy to embedding inputs before they are sent to Gemini's embedding endpoint.
Enforcement model
Every decision can use normalized content plus tenant, identity, team, application, provider, model, stage, and configured policy metadata.
01Translate normalized roles, parts, tools, and system instructions to the Gemini API.
02Consume Gemini SSE and evaluate normalized accumulated candidates before guarded live release.
03Inspect normalized embedding input using the same tenant runtime and policy ecosystem.
04Map Gemini token metadata into consistent audit, analytics, and cost-governance records.
In the request path
Policies remain modular packages. The core resolves, executes, contains, explains, measures, and audits them.
Authenticate the Entrovik API client and resolve tenant policy
Normalize generation or embedding input and execute the ordered request policies
Convert the allowed request through the native Gemini adapter
Normalize candidates, function calls, finish reasons, and token metadata
Execute response policies and return a compatible response with content-free audit evidence
Technical FAQ
Yes. The native Gemini adapter includes batch embedding conversion and usage-safe response handling.
Policies receive normalized multimodal metadata and text parts. Binary image interpretation requires a policy designed for that capability; no network or host access is granted by default.
No. Configuration points to an environment or managed secret reference rather than encouraging literal credentials.
Yes. Provider choice remains separate from the policy pipeline, allowing common governance across Gemini, OpenAI-compatible local endpoints, and other adapters.

Put it in front of a real workflow
Bring one provider path, one policy requirement, and the architecture your reviewers need to trust.