Run AI without sending data to someone else's cloud
Self-hosted deployment on Docker, PostgreSQL, and Redis. Agent workloads run inside your perimeter. Your data, your logs, your retention policy.
Horizon Portal gives operations and governance teams a single surface for AI-assisted workflows, fleet visibility, and policy control. Self-hosted, by default.
100%
of your data stays inside your perimeter. No cloud assumption, no silent egress, no dependency on a vendor's retention policy.
Self-hosted deployment on Docker, PostgreSQL, and Redis. Agent workloads run inside your perimeter. Your data, your logs, your retention policy.
Windows, Linux, macOS, and container workloads in a single inventory. Patch state, certificate expiry, vulnerability posture, and compliance checks, surfaced once and acted on centrally.
Usage and policy controls sit under every AI action. Caps by user, team, or workflow. Audit trails by default. Defensible in a compliance review.
Unified inbox for agents, tickets, alerts, and change workflows. AI-assisted triage, summarisation, and first-pass response, with human approval gates where they matter.
Customer-facing status and service pages as a first-class feature. Show the parts of your operation customers benefit from seeing. Hide the rest.
Most technology ESG reporting breaks at one of two points: data quality, or access to it. If your numbers can't be traced from source telemetry to reported figures, they're hard to defend under real scrutiny.
Horizon Portal is instrumented differently. The included ESG agent runs across the heterogeneous fleet most operators actually have on the floor — Windows, macOS, Linux, Proxmox, pfSense — and joins primary kilowatt readings to your grid-emission factor and your contracted electricity rate. You get measured energy, Scope 2, and cost views, with the chain of custody every link of the way.
For AI workloads specifically, the same chain runs end-to-end: the token a user generated, the GPU-second that produced it, the kilowatt the rack drew, the grid factor your jurisdiction publishes, and the CO₂e you put on the sustainability report. Cloud AI shows you the bookends; Horizon Portal shows you everything in between.
80.1 kWh
Measured across 10 endpoints — Windows, macOS, Linux, Proxmox, pfSense — on our own infrastructure.
16.6 kg CO₂e
UK grid factor; full provenance in the disclosed-factors table.
£24.03
Ofgem UK 2024 unit rate. Replace with your own contracted rate at deployment.
From our own kit, not a customer reference. We dogfood the ESG agent before we deploy it on yours. See the ESG agent product page →
A single ESG agent runs across Windows, macOS, Linux, Proxmox, and pfSense, with primary counters where the platform exposes them and labelled estimation where it doesn't. Other hypervisors and operating systems are on the roadmap. See the ESG agent →
Each completion, summarisation, or agent run is joined to the GPU time, CPU time, and kWh that produced it. Power draw and token throughput appear on the same dashboard, timestamped per workflow. The same view your engineering team uses to tune cost is the view your sustainability team uses to report.
Horizon Portal applies your region's grid-emission factor (or your own contractual one) to convert kWh into CO₂e, and your contracted electricity rate to convert kWh into £. Outputs are exportable as a CSV trail with timestamps, workload IDs, factor sources, and method-accuracy badges. The kind of thing an auditor can trace.
For every AI workload, the Portal shows what the same tokens would have cost (in money and in carbon) on the major cloud providers, using published or inferred emission factors. You get the comparison you need to defend a self-hosting decision to a CFO and a sustainability officer in the same meeting.
If your AI strategy has to survive both a CFO and a sustainability officer, "the vendor publishes an average" is not an answer. Horizon Portal makes it a trail.
Horizon Portal instruments what you already own; it isn't a carbon-neutral claim, a certification, or an offset programme. It's a trail a sustainability team can use.
Standard container stack: Docker, PostgreSQL, Redis, with secrets managed through environment configuration or an integrated vault. Advanced integrations (identity providers, SIEM, ticketing) and agent-side modules are added based on environment requirements.
Deployment targets: on-premises, private cloud, or a regulated hybrid. Reference architectures available for common environments on request.
A demo takes about 30 minutes and is scoped to the workflows you care about. We'll walk a real scenario, not a scripted tour.