Product

Watch LLM Capsule run on a real enterprise workflow

Two minutes — see a real document encapsulated, sent to an external LLM, and restored back into the originating workflow. No marketing words. The actual product.

Technical view · zone-based architecture

The same architecture, in technical view

For architects and security reviewers — the full zone-based view of how operational data, encapsulation, and how any LLM interacts.

01 Source Data
Corporate Internal Network
On-prem DB · Enterprise Systems
Unstructured
DB1
Customer Data
Personally Identifiable Info
DB2
Ticket Data
CS Tickets / Status
DB3
Detail Data
Unstructured Claims
Raw Input Fields
Customer David Lawson ID
Ticket CS-4203 CD
Free Text Shipping delayed... BD
×
PII guardrails protect fields. Enterprises run on structures. We are not criticizing PII filters. We handle a different category of data — table schemas, cross-references, alarm sequences, and ticket threads that simple field-level masking cannot preserve.
ERP
SAP·Oracle
CRM
Salesforce
RAG
Vector DB
Legacy
Oracle
Ticket
Jira·SN
DMS
SharePoint
REST · gRPC · JDBC · Graph API
Zero System Modification Integrates via a single API call with zero modifications to existing ERP, CRM, or legacy systems
02 Enterprise Environment Execution
Unstructured Data In
02 DP Encapsulation
DMZ — Differential Privacy
Same Org · EU Region · GDPR Ready
Encapsulation Flow
IN
Raw Input
Unstructured Data
PROCESS
DP Engine
Differential Privacy
OUT
Encapsulated
Token Capsule
Encapsulation ✓ Protected
Name * * * * * * * ID
Champ Id CS-* * * * CD
Free Text [tokenized...] BD
DP Engine epsilon-DP Active
Noise Injection (Laplace)
k-Anonymity Enforcement
Semantic Tokenization
Free-Text NER Masking
DMZ Guarantee Goes beyond simple encapsulation. Differential privacy techniques make original sensitive data mathematically irreversible
01 Structure-Preserving 05 Zero Exposure & Audit
Protected Data Out
03 AI Processing
In-House Team
Same Org · Anonymized LLM Proxy
LLM Pipeline
LLM-a-Proxy Anonymized Routing
Path A · External
Public cloud Region-hosted
Path B · On-prem
Private On-prem
swap any model — capsule contract stays the same
No Direct Access to Source DB AI teams never touch the source database. They only receive structure-preserved, differentially-private data
Privacy Isolation Module
PDESC / ISOLA
Privacy Descriptor
Isolated Computation Zone
Output De-identification
Re-identification attempts contained · Output validated
Compliance
EU GDPR EU Region
01 Structure-Preserving 05 Zero Exposure & Audit
AI Response (tokenized)
04 Local Auto Reconstruction
Local — Auto Reconstruction
Internal Only · No External Egress
Reconstruction Flow
IN
AI Token
Tokenized Response
PROCESS
Reconstruction
Local Restoration
OUT
Original Value
Business-Ready
Token → Original
Customer David Lawson ID
Ticket CS-4203 CD
Details Shipping delayed... BD
Reconstruction Local Only
Token Map Lookup
Original Value Restore
Context Re-binding
Output Validation
Local Reconstruction Guarantee Token map exists only in local storage · Delivers Business-Ready Output instantly
Output Properties
Original Values Restored
Zero External Exposure
Context Fully Preserved
Business-Ready Output
Auto Restore Local Only Data Residency
03 Business-Ready Reconstruction 04 Enterprise Context Control 06 Time-Shifting Policy
6 Core Capabilities
What Makes The Workflow Run
01
Structure-Preserving
Tables, logs, cross-references, and alarm sequences stay intact. AI reads structure, not just text.
02
Enterprise Environment Execution
Deploys inside your environment. Connects via API, SDK, connectors, or reverse proxy. No traffic re-routing.
03
Business-Ready Reconstruction
AI output is restored with real values. The result goes straight back to the originating ticket or workflow.
04
Enterprise Context Control
Your IT admin defines what counts as sensitive. Custom markers, regex rules, and tier policies. Set in 5 minutes.
What Gets The Approval
05
Zero Exposure & Audit
Raw operational data stays inside. Every action logged, timestamped, SIEM-exportable.
06
Time-Shifting Policy
Sensitivity changes over time. Capsule versions every marker and policy for continuous compliance.
01 and 02 lead the conversation. 05 and 06 anchor the approval.
Zone 1 · Corporate Internal Network

Where the operational systems already live

Existing enterprise systems — ERP, CRM, Ticketing, DMS / ECM, Legacy DB, RAG Pipeline — stay in place. Nothing migrates. Capsule reads from them via REST, gRPC, JDBC, or Graph API depending on the source.

Zone 2 · DMZ — Demilitarized Zone

Where encapsulation happens

The Enhanced Encapsulation Layer detects sensitive elements, replaces them with safe tokens using structure-preserving, differential-privacy-based protection, and hands the capsule to the routing decision. Original values stay behind, retained in the local token map.

Zone 3 · In-House Team

Where governance and routing happen

Organizational policy, permissions, and domain context decide where the capsule is processed — an approved external LLM (Path A) or an on-prem local model (Path B). The decision is policy-driven per workflow, with full audit retained inside the organization.

Zone 4 · Local — Auto Reconstruction

Where the AI response becomes Business-Ready output

The AI response is automatically reconstructed from token to original value inside the organization only. Data that left the trust boundary cannot be reconstructed externally. The restored output is delivered back into the originating workflow.

Interactive product tour

Five steps. One real document. Real output.

The same capsule mechanism runs across telecom, healthcare, finance, defense, legal, and OT. Below: a contract review workflow. The raw document never leaves your environment.

NOC Ticket · INC-2025-0427
Circuit ID:ACME-CKT-4821-NYC
Device IP:10.44.72.31
Contract Ref:MSA-ACME-2025-0312
Site Code:NYC-DC1-FLOOR3
Service circuit ACME-CKT-4821-NYC reported signal degradation on device 10.44.72.31. Per master agreement MSA-ACME-2025-0312, clause 4.2 mandates log retention for 36 months. On-site verification scheduled at NYC-DC1-FLOOR3 pending change approval.
Analyze this incident for root cause and recommended actions.
✦ Run Capsule
Step 01 — Point at the source

Reads the document where it already lives

LLM Capsule runs inside your environment and reads documents from the systems already there — SharePoint, Jira / ServiceNow, Salesforce, Oracle ERP, internal NOC console, or your own portal. No data migration. No external pipe. No architectural change.

Existing systems invoke Capsule from inside the environment via REST / gRPC / JDBC / Graph API / on-prem API / embedded SDK / Slack App.

In-environmentNo data egressExisting sources
Reads the document where it already lives
Step 02 — Define policy

Pick the filters your business cares about

Pick from the starter pack — project codes, contract refs, network IDs, mission refs, financial terms, vulnerability labels — or write your own. Filters can be added, removed, and time-shifted tomorrow without redeploying. Every policy version is logged.

11 starter markersCustom regexPolicy versionsRBAC scope
Pick the filters your business cares about
Step 03 — Encapsulate

Sensitive elements replaced. Structure preserved.

Inside the DMZ — Demilitarized Zone (Zone 2 of the four-zone architecture), sensitive elements are replaced with structure-preserving placeholders by the Enhanced Encapsulation Layer. Differential-privacy-based encapsulation (epsilon-DP, Laplace noise, k-anonymity, NER replacement) reduces re-identification risk. Tables, cross-references, and document hierarchy survive intact. See the four-zone architecture

epsilon-DPLaplace noiseNER maskingStructure preserved
Sensitive elements replaced. Structure preserved.
Step 04 — Process

Any LLM. Path A or Path B.

The capsule (only the capsule — never the original) is routed through your approved external LLM (ChatGPT, Claude, Gemini, Perplexity) or to an on-prem local lightweight model for air-gapped workflows. Path is policy-driven per workflow.

Path A · ExternalPath B · On-premPolicy-routed
Any LLM. Path A or Path B.
Step 05 — Restore

AI output comes back business-ready

The AI's response is auto-restored locally — token map lookup, original value substitution, context re-binding, output validation. Real names, real figures, real references appear in the original ticket. Token map never leaves the enterprise. End user sees a finished, production-ready output.

Local restoreContext re-bindingOutput validationAudit logged
AI output comes back business-ready
Performance — measured on real enterprise documents

The numbers behind the demo

2,200-character document benchmark. Tested across finance, healthcare, legal, and public sector workflows.

0.12s
Per-page processing latency

That's 120 milliseconds from raw document to encapsulated capsule — fast enough to plug into real-time NOC alerting, claims intake, and clinical workflows without breaking SLA. Most enterprise AI pilots stall on latency. We don't.

100%
Restoration rateEvery encapsulation has a reversible local mapping. No ambiguity, no manual reconstruction.
98%
Output similarityCompared to AI processing the original document. Restoration preserves business meaning.
98.1%
Detection accuracySensitive entity detection across structured and free-text fields, including custom markers.
99.14%
Workflow accuracyEnd-to-end correctness — from raw input to restored output in production workflows.
Workflow gallery

Same product. Six industries. Real customers.

Each card below is a real workflow LLM Capsule runs in production. Click for the full case story.

Telecom

NOC incident analysis on production traffic

RCA generation on live ticket data with device IDs, circuit IDs, site references, alarm sequences, SLA-impact references, and subscriber identifiers encapsulated locally. No raw operational data exposure to external LLMs.

SK Telecom · Deutsche Telekom T Challenge 2026 — Top 12
Healthcare

Radiology report drafting with PHI never leaving

AI drafts radiology summaries from real clinical workflows. PHI encapsulated locally; restoration happens inside the hospital network. HIPAA-aligned.

Ewha Womans University Medical Center (EUMC)
Finance / Insurance

AI claims processing with real customer data

AI-powered claim classification, damage assessment, and fraud detection on real policyholder data. No customer data leaves the insurer's environment.

Kyobo · DB Insurance · IBK
Public Sector / Defense

Mission brief drafting on classified workflows

AI drafts intelligence briefs and operational summaries on classified data. On-prem local execution path — zero external transmission. Full audit trail under command control.

Ministry of National Defense (South Korea)
Operational governance

Admin console — every event, every policy, every model

Enterprise AI governance is not a marketing claim. It's a console your audit team logs into.

AuditPoliciesTokensDetectionModels
10:24:18INC-24091 · NOC-team-v2 · Path Arestored
10:24:11CLM-77241 · finance-v3 · Path Arestored
10:23:58MR-440-Z · defense-v1 · Path Brestored
10:23:42Policy NOC-team updated to v2policy
10:23:30Detection · custom marker addedpolicy

One pane. Five tabs. Full chain of custody.

Every encapsulation, processing, and restoration event lands here. Audit teams can replay any event end-to-end — what was protected, which policy version was active, which model processed it, what was restored.

  • Audit every event with timestamps and policy version
  • Policies version history, scope, and RBAC
  • Tokens model usage, cost, and per-team breakdown
  • Detection what was classified as sensitive, and how
  • Models health, throughput, comparative output quality
Capability 06 · Deep dive

You define what's sensitive — and you can change it tomorrow.

Yesterday it was network logs. Today it's M&A code names. Next quarter it's a new regulator's spec. Standard PII categories don't move; your business does. LLM Capsule lets your team define, add, remove, and version confidentiality markers as your operations and regulatory landscape evolve — with full audit trail of which marker was protected when.

DEFINE

Beyond generic PII

Project codes, deal terms, internal IDs, contract references, network identifiers, OT asset IDs, mission refs. Your team defines the markers — not a vendor's fixed list.

VERSION

Time-shift the policy

Add a new marker today, retire one next quarter. Policy versioning + immediate enforcement. Audit log records exactly which marker was active for every encapsulation event.

SCOPE

Per workflow, team, data type

NOC team, oncology unit, OT operations, M&A — different policies, same governance. RBAC + scoped enforcement + per-policy audit. One LLM Capsule, many policies.

See it on your own documents.

Bring your real workflow. We'll set up Capsule on a sample document in your environment within 30 minutes.

Email : contact@cubig.ai

CUBIG LTD (United Kingdom)

Company Number: NI735459
Address: 21 Arthur Street, Belfast, Antrim, United Kingdom, BT1 4GA


CUBIG CORP (Republic of Korea)

Business Registration Number : 133-81-45679

E-Commerce Registration : 2023-Seoul-Seocho-2822

Address: 4F, NAVER 1784, 95, Jeongjail-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, Republic of Korea

©️ 2026 CUBIG Corp. All rights Reserved.

Consent Preferences

Email : contact@cubig.ai

CUBIG LTD (United Kingdom)

Company Number: NI735459
Address: 21 Arthur Street, Belfast, Antrim, United Kingdom, BT1 4GA


CUBIG CORP (Republic of Korea)

Business Registration Number : 133-81-45679

E-Commerce Registration : 2023-Seoul-Seocho-2822

Address: 4F, NAVER 1784, 95, Jeongjail-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, Republic of Korea

©️ 2026 CUBIG Corp. All rights Reserved.

Consent Preferences

Email : contact@cubig.ai

CUBIG LTD (United Kingdom)

Company Number: NI735459
Address: 21 Arthur Street, Belfast, Antrim, United Kingdom, BT1 4GA


CUBIG CORP (Republic of Korea)

Business Registration Number : 133-81-45679

E-Commerce Registration : 2023-Seoul-Seocho-2822

Address: 4F, NAVER 1784, 95, Jeongjail-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, Republic of Korea

©️ 2026 CUBIG Corp. All rights Reserved.

Consent Preferences

Email : contact@cubig.ai

CUBIG LTD (United Kingdom)

Company Number: NI735459
Address: 21 Arthur Street, Belfast, Antrim, United Kingdom, BT1 4GA


CUBIG CORP (Republic of Korea)

Business Registration Number : 133-81-45679

E-Commerce Registration : 2023-Seoul-Seocho-2822

Address: 4F, NAVER 1784, 95, Jeongjail-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, Republic of Korea

©️ 2026 CUBIG Corp. All rights Reserved.

Consent Preferences

Email : contact@cubig.ai

CUBIG LTD (United Kingdom)

Company Number: NI735459
Address: 21 Arthur Street, Belfast, Antrim, United Kingdom, BT1 4GA


CUBIG CORP (Republic of Korea)

Business Registration Number : 133-81-45679

E-Commerce Registration : 2023-Seoul-Seocho-2822

Address: 4F, NAVER 1784, 95, Jeongjail-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, Republic of Korea

©️ 2026 CUBIG Corp. All rights Reserved.

Consent Preferences