Cloud
FortEmerald runs centrally across distributed customer sites, providers and assets.
- Central policy and evidence
- Fast connector rollout
- Usage-aligned scale
The control boundary follows the operation.
FortEmerald places policy, model access, credentials and evidence where the customer needs them—centrally, at the edge, on-premise or inside an isolated environment.
Choose the boundary before the infrastructure.
The same eight layers can be placed differently for latency, residency, connectivity and sovereignty.
Hybrid
Central governance coordinates local Copper connectors and machine-side safety.
- Low-latency local action
- Central fleet visibility
- Resilient edge operation
On-premise
The customer hosts runtime, models, policy, keys, connectors and evidence.
- Customer-controlled data path
- Internal model routing
- Local security operations
Isolated
A self-contained deployment runs without required public-cloud or external-model access.
- Disconnected operation
- Local update approval
- Export-controlled evidence
Machine safety stays local and authoritative.
FortEmerald governs whether an action is released and under what limits. Certified flight, motion, industrial and emergency-stop controls remain authoritative at the machine.
Enterprise policyDefines approved users, agents, models, actions, locations and operating windows.
FortEmerald authorizationBuilds and signs the exact action package after the request passes policy.
Local enforcementThe connector and machine controller apply local interlocks, readiness and safety state.
Evidence returnThe result, intervention and final state rejoin the complete control record.
Limit trust at every boundary.
Controls apply before context is disclosed, before AI is called, before an instruction is released and after the destination reports a result.
Strong identityPeople, workloads, agents and machines receive distinct identities and permissions.
Least contextModels receive the minimum approved data package for the task.
Least actionConnectors expose narrow operations instead of broad infrastructure or device control.
Protected secretsCredentials stay in the control environment and are never placed in model prompts.
Complete evidenceRequest, policy, decision, command, result and state remain linked.
A practical path to post-quantum security.
Long-lived machine estates need cryptographic controls that can change without redesigning every connector or workflow.
TransportTLS 1.3 protects supported service links, with deployment-specific endpoint and browser compatibility.
Key separationAlloy keeps workload, connector, signing and evidence-key responsibilities distinct.
Algorithm policyCryptographic suites are selected by deployment policy rather than embedded throughout business logic.
PQ migrationNIST-standard post-quantum algorithms can be introduced through staged hybrid or replacement profiles as the customer environment supports them.
Copper connectors keep access narrow.
Each connector maps a governed FortEmerald action to the smallest practical operation offered by the destination.
| Destination | Connector responsibility | FortEmerald controls | Local authority |
|---|---|---|---|
| Cloud infrastructure | Create, resize, stop or inspect a named resource | Tenant, project, template, budget, region, expiry | Provider quota, availability and platform safety |
| Drone fleet | Dispatch an approved mission package and receive state | Operator, airframe, geofence, time, sensors, purpose | Flight controller, collision avoidance and emergency response |
| Industrial control | Write an allowed setpoint or trigger an approved sequence | Asset, range, rate, maintenance state and human checkpoint | PLC, interlock, process safety and emergency stop |
| Digital workflow | Transform, approve, publish or withdraw a named object | Creator, rights, content class, model and destination | Marketplace, storage and payment rules |
The connector catalog is expanding. New integrations are delivered against the destination’s documented interface, customer policy and test environment.
Define the boundary, then map the route.
We’ll identify where policy, AI, secrets, connectors and evidence need to run for your first workflow.
Plan your deployment