Loading…
GyroX uses cookies that are essential to run the service. With your consent, we also use analytics cookies to improve the product. Privacy Policy
Dual-mode means you don't have to choose. Run on the native ledger as your keystone, or coexist with SAP, Oracle, NetSuite or Douzone through hexagonal adapters—keeping the systems your auditors and regulators already trust at the edges, while operations, the twin, IoT and AI run on one ontology in the middle.
Don't rip it out — coexist with your ERP at the regulated edges
The heart of dual-mode. Run on the native ledger (GL), or coexist via adapters while keeping SAP, Oracle, NetSuite or Douzone at the regulated edges. E-tax (HomeTax / Popbill) and banking (SWIFT/SEPA/ACH and bank EDI) connect through hexagonal ports.
Dual-mode coexistence — keep the regulated edge via an external-ledger adapter.
Dual-mode coexistence — align with the Oracle ledger via an adapter.
Mid-market ERP coexistence — align postings through the external-ledger port.
E-tax invoice issue/receive — port contract defined, pre-live-certification.
Payment/receipt bank connectivity — idempotent payment port, direction stage.
Orders reach the ledger and inventory without a break
Ingest commerce-channel orders and payments into the O2C flow, aligning revenue and receivables to the ledger. Shopify and Naver Pay / SmartStore connect via adapters.
Order/payment → O2C mapping — adapter contract, direction stage.
Korean commerce order ingestion — port-based, pre-live-certification.
Notifications and approvals flow to where your team works
Approval gates, notifications and work orders flow into mail and collaboration tools. Every dispatch routes through one MessagingPort and is audited.
Email notification/approval dispatch — MessagingPort adapter.
Korean collaboration notifications — port-based, direction stage.
Channel notifications / approval flow — adapter contract.
Team notifications / approval flow — adapter contract.
Sensor signals reach the twin through one inbound port
Ingest sensor telemetry through one inbound port (iotgateway), wired to the digital twin and decision trail. BMS controllers, KEPCO/utility APIs and MQTT sensors connect through standard contracts. IT and OT stay separated.
Building-automation setpoints/telemetry — via approval gate.
Power/utility meter ingestion — energy-lineage port.
MQTT telemetry — ingested to the twin via one inbound port.
Enterprise SSO and automatic provisioning, kept safe
Connect enterprise IdPs via SSO/SAML and automate user provisioning with SCIM. JWT validation is enforced through a single entry point.
SAML 2.0 / OIDC enterprise SSO — single validation entry point.
User provisioning/deprovisioning automation — direction stage.
Entra ID OIDC sign-in — live in the dev environment.
Wire 2D/3D viewers through one standard integration contract
Connect external 2D/3D viewers through a published-API + event-bus integration contract. Map IFC, Brick and Forge onto the core relations.
BIM IFC models → asset-lineage mapping — viewer integration contract.
Brick schema → 1:1 registration onto the 25 core relations.
3D viewer embed — integration contract, direction stage.
Swap providers freely behind one AI Gateway
Every model call routes through one audited AI Gateway. With no direct LLM calls in application code, providers and models are swappable without touching operations—with priority fallback, per-tenant keys (BYOK), token/cost metering and streaming.
AI Gateway provider — live entry point.
AI Gateway provider — live entry point.
AI Gateway provider — live entry point.
AI Gateway provider — live entry point.
AI Gateway provider — live entry point.
Local / on-prem inference provider — live entry point.