AIGQLUnify • Architecture patent pending
Your REST · Our Graph
Build

Gateway today. Subgraph tomorrow. Your call.

Two on‑ramps, one runtime: bring Apollo subgraphs or generate from OpenAPI. Same masking, same audit, same PDP.

How we leverage both paths

Path A — Bring subgraphs. Register subgraphs; we respect entity keys. AIGQLUnify enforces masking at field resolution and emits spans.

Path B — Generate from OpenAPI. Upload specs, pick fields; we emit Apollo‑compatible subgraphs automatically—joins + policy built‑in.

Upload OpenAPI and select fields
Upload OpenAPI specs and choose response fields to expose — SDL is generated for you.

AI in Federation (joins + smart schema)

AI joins and Smart schema
Join suggestions and SDL hints — generate with joins, then ship as a subgraph.

Field‑level masking in action

Field level masking
On every execution, DP uses the current plan/SDL. If a field is sensitive, the subgraph calls PDP and applies REDACT | PARTIAL | HASH at field resolution. The response and spans reflect the decision.

End‑to‑end telemetry

OpenTelemetry spans in Jaeger
End‑to‑end OpenTelemetry: spans with PDP obligations visible in Jaeger.

What ships on day one

  • REST → GraphQL projection per workspace
  • Federation‑ready SDL, publishable as subgraphs
  • PDP/PEP with ABAC & field‑level masking
  • OTLP export to Jaeger; logs & metrics embedded with policy stamps
Ready to see both modes in one runtime?
Watch the demo: REST → GraphQL + Apollo subgraphs, governed by PDP/PEP and traced end‑to‑end.
Play demo