Endpoint / MDM
Jamf Pro · Microsoft Intune · Kandji · Mosyle · Workspace ONE · Hexnode
Device truth: enrolment, encryption, OS level, compliance, last check-in, dispatch outcome.
Digital Operations
Your tools are instruments. Lojycal is the workstation.
A producer does not open twelve apps to make a record. They patch every instrument into one desk, hear them in time, and run the whole record from one workstation. Lojycal does that for business operations: every SaaS, MDM, HRIS, finance and storage system becomes a Digital Operational Instrument, patched into one workstation where they finally play together.
Three words, one theory
- DOI01
Digital Operational Instrument
Every integrated tool. Jamf, Intune, Kandji, Okta, Entra, Personio, BambooHR, DATEV, Box, SharePoint, Jira, Slack — each one is an instrument with a voice, a range and a tuning.
An instrument is not a tab. It is a signed connection that emits signal and accepts writes.
- DOWin02
Digital Operations Window
Every module in the sidebar. Asset Inventory, Employee Governance, Procurement, Financials, Patch, Policy, Trust — each is a window onto the same session, mixed for a different job.
Finance and IT look at different windows and still see the same take, at the same timecode.
- DOW03
Digital Operations Workstation
The desk itself. One tenant, one graph, one audit trail. Everything routed, timed, versioned and recorded — not a wall of disconnected consoles.
The workstation is where the mix is decided. Instruments only supply the parts.
The rack
Instruments are grouped by family. Each strip contributes a specific signal to the graph — never a screenshot, never a CSV, never a stale nightly pull.
Identity
Okta · Microsoft Entra · Google Workspace · SAML / SCIM
Who exists, what they can reach, when access was granted and when it must end.
People / HRIS
Personio · BambooHR · Workday · SAP SuccessFactors · Deel
Joiners, movers, leavers — the clock every downstream workflow runs against.
Finance / ERP
DATEV · Sage · QuickBooks · Xero · vendor order transports
CapEx, OpEx, purchase orders, invoices and book value against the asset that carries them.
Storage
Box · SharePoint · Dropbox · Google Drive
Where the evidence lands: contracts, certificates, disposal proofs, signed evidence packs.
Work / Collaboration
Jira · Linear · Asana · Slack
Requests and approvals in the tools people already live in, scored against benchmarks.
Infrastructure
AWS · Azure · GCP
Cloud footprint, spend drift and the accounts nobody remembers opening.
Native plane
Lojycal agent · Cookie Jar browser extension
Sub-60s posture from the device itself, with no MDM required.
Signal flow
01
The instrument emits
A webhook, a heartbeat, a scheduled pull or a signed agent check-in. Every ingress is authenticated and deduplicated.
02
Lojycal normalises
Serial numbers, emails, hostnames and cost centres are reconciled into one identity per person, per device, per contract.
03
The graph resolves
Employee → device → licence → contract → cost centre → lifecycle stage. One edge set, one source of truth, per tenant.
04
A window renders it
Whichever module you have open shows the same resolved state, tier- and role-aware, with nothing cached in your browser.
05
A workflow writes back
Approve, dispatch, revoke, book, retire. The write goes back out through the instrument and lands in the WORM audit ledger.
Why a workstation beats a dashboard
Dashboards read. Workstations operate. A dashboard tells you 41 laptops are out of policy; a workstation lets you select them, push the fix through the right MDM, watch each device confirm, and file the evidence — without leaving the take.
Write-back, not read-only
Every instrument that can accept a write is wired for it: MDM commands, HRIS pushes, ERP order dispatch, IdP revokes. Read-only integrations are labelled as such, so nobody assumes an action landed.
Confirmation over optimism
A dispatch is not done because the API returned 200. Lojycal re-reads the instrument and only then flips the state. No force-green fallback, anywhere.
One timecode
Finance, IT, HR and the auditor look at the same resolved graph. There is no reconciliation meeting because there is nothing to reconcile.
Everything printed
Actions, approvals, overrides and failures land in an append-only ledger with actor, target and before/after — the master you hand to the auditor.
Governance on by default
- Per-org row-level security on every table — no cross-tenant read is possible, ever.
- Cloud database is the source of truth; the browser stores preferences, never records.
- Webhook ingress is HMAC-signed and replay-protected; the bundled public key is never a gate.
- Circuit breakers and dead-letter queues on every dispatch path, so a failing instrument cannot silently drop writes.
- Audit ledger is WORM — update and delete are refused for everyone, platform admins included.
- AAL2 step-up on privileged actions when the workspace enforces it.
One desk. Every instrument. One workstation.
Stop mixing your operations in twelve browser tabs. Patch the instruments in once and run the whole business from the workstation.