Skip to main content
HikmaAI

HikmaEdge

AI coding has moved to the workstation. Your security boundary should move with it.

Coding agents can send source code, prompts and internal context directly from developer machines to model providers — outside AI gateways that only protect centrally routed traffic.

HikmaEdge adds an inline HikmaAI policy boundary for governed coding-agent traffic before it reaches the model provider.

Governed Traffic Path

  1. Coding Agent

    Codex · Gemini · Claude Code

  2. HikmaEdge

    Local policy boundary

  3. HikmaAI Gateway

    Inspection · policy · audit

  4. Model Provider

    Provider endpoint

01 · The Control Gap

The AI gateway only governs the traffic that reaches it.

When coding agents connect directly to model providers, that traffic may sit outside the central AI controls an organisation has already deployed.

01 · No Enforced Route

Policy cannot govern traffic it never sees.

A coding agent configured to connect directly to a provider can bypass a centrally deployed AI gateway. HikmaEdge creates a governed route for supported coding-agent traffic.

02 · Provider Credentials

Developer-held credentials need a governance path.

Coding agents may authenticate directly to model providers using locally configured credentials. HikmaEdge governs traffic sent through the configured path.

03 · Incomplete Audit Evidence

An audit trail needs an inspection point.

Without traffic crossing an organisational control point, reconstructing what was sent, what policy applied and what happened next can be difficult.

02 · How HikmaEdge Works

Change the route. Not the workflow.

HikmaEdge extends the HikmaAI security boundary to the workstation without creating a separate developer security workflow.

What Runs Locally

HikmaEdge receives governed coding-agent traffic at the workstation and routes it through the HikmaAI security boundary.

What Runs Centrally

HikmaAI Gateway provides central inspection, policy and governance capabilities.

Credentials

Provider credentials remain part of the developer's configured coding-agent setup while HikmaEdge governs the traffic path.

Outage & Bypass

Availability and bypass behaviour follow the organisation's configured HikmaEdge and endpoint security policy.

03 · One Platform. Three Questions.

Observe. Control. Govern.

HikmaEdge brings governed coding-agent traffic into the same HikmaAI operating model used across the agentic stack.

Observe

What are our governed coding agents sending?

  • Requests and destinations
  • Policy outcomes
  • Security findings
  • Structured audit records

Control

What are they allowed to send?

  • Data-protection policies
  • Provider and model controls
  • Prompt and content inspection
  • Budget controls

Govern

Can we prove what happened?

  • Sent
  • Inspected
  • Allowed or blocked
  • Transformed

04 · Deployment & Compatibility

Start with the route.

For Codex, Gemini and Claude Code, adoption is designed around changing the model endpoint or base URL rather than rewriting the developer workflow.

01

Supported Coding Agents
Codex · Gemini · Claude Code

02

Change The Route
Point the coding agent at HikmaEdge.

03

Keep The Workflow
No SDK or agent rewrite.

04

Use Your HikmaAI Deployment
Self-hosted · SaaS · private cloud

Not Another Observability Dashboard

Passive monitoring tells you what happened. HikmaEdge puts policy in the governed request path before onward routing.

Request Demo

Stop hoping.
Start proving.

Request a 30-minute demo. We walk your team through the threat model for your specific agentic footprint — and what controlling it looks like.

Get in touch.