SPB Git

Repository Public License

spborix-monitor

ORIX Monitor — native macOS system monitoring, diagnostics and performance intelligence. Every metric measured, nothing invented.

12 entries at the root
History

Latest commit chore: standardize SP Boucher source headers and attribution 83f517e

NameLast commitUpdated
App chore: standardize SP Boucher source headers and attribution
docs docs: publish v1.0.0 — public repository, release links, verified downloads
Packages chore: standardize SP Boucher source headers and attribution
Scripts chore: standardize SP Boucher source headers and attribution
UITests chore: standardize SP Boucher source headers and attribution
.gitignore feat: telemetry core (collectors, time-series store, alerts, findings, reports) with 79 tests
.spb-source-governance.toml chore: standardize SP Boucher source headers and attribution
CLAUDE.md chore: standardize SP Boucher source headers and attribution
LICENSE release: ORIX Monitor 1.0.0 (build 1) — notarized macOS build
project.yml chore: standardize SP Boucher source headers and attribution
README.md docs: publish v1.0.0 — public repository, release links, verified downloads
RELEASE-REPORT.md docs: publish v1.0.0 — public repository, release links, verified downloads
README.md View source
ORIX Monitor icon

# ORIX Monitor

Understand Every Pulse of Your Mac.

A native macOS system monitor that shows what your Mac is really doing — CPU, GPU, memory, storage, network, processes,
power and thermal state — with the source of every number, a local history, alerts, findings and reports.
Every metric is measured. Everything the system does not expose is said to be unavailable, never invented.

Author: Simon-Pierre Boucher

macOS Apple Silicon Swift SwiftUI Telemetry Privacy Accounts

Version Core tests UI tests Notarization Gatekeeper DMG Dependencies Entitlements Languages License


ORIX Monitor dashboard in Dark Mode, showing live CPU, memory, GPU, thermal state, battery, network and disk activity

The dashboard on a MacBook Pro (M5 Max). Every figure in every screenshot of this page is a live reading captured from the signed app; none is staged.

# ⬇ Download ORIX Monitor 1.0.0 (DMG, 3.5 MB)

ZIP · SHA-256 checksums · Release notes · All releases

Badge values are not live. They are static and were written from the runs recorded in RELEASE-REPORT.md on 2026-11-21.


# Contents

  1. Overview · 2. Product philosophy · 3. Application preview ·
  2. System dashboard · 5. CPU · 6. GPU · 7. Memory ·
  3. Disk · 9. Network · 10. Processes · 11. Power ·
  4. Thermal · 13. Menu bar · 14. History · 15. Alerts ·
  5. Insights · 17. Reports · 18. Metric sources ·
  6. Metric availability · 20. Technology stack · 21. Architecture ·
  7. Installation · 23. Build · 24. Testing · 25. Benchmarks ·
  8. Overhead · 27. Privacy · 28. Accessibility · 29. Localization ·
  9. Roadmap · 31. Release status · 32. Known limitations ·
  10. ORIX ecosystem · 34. License

# 1. Overview

ORIX Monitor is one application that does the work of an activity monitor, a menu bar meter, a history recorder and a diagnostic report tool.

It gives you How
A live picture of the Mac 13 pages: overview dashboard, CPU, GPU, memory, disk, network, processes, power, thermal, history, insights, alerts, reports
A memory A local SQLite time-series store with three retention tiers (every sample, per-minute, per-hour)
Answers Findings derived from stored history, each with its evidence, threshold, duration and a suggested next step
Warnings Alert rules with a hold time, cooldown and snooze; Notification Center is optional
Something to hand over Reports in PDF, Markdown, CSV and JSON, listing units, methods, sampling and data gaps
A glance A configurable menu bar item with mini charts and a quick panel

It is written in Swift 6 with SwiftUI and Swift Charts, uses only Apple frameworks, runs without an account, without administrator rights and without any network connection of its own.

# 2. Product philosophy

  1. Measured or absent. A number is shown only if a system interface produced it. There are no simulated sensors, no decorative gauges and no placeholder controls.
  2. Every value says where it comes from. Each page ends with its sources and methods, read from the same catalogue the code uses (Metric.swift).
  3. Four honest labels. Measured, Derived, Estimate, Best effort. "Best effort" marks values read through a public API from a property whose name Apple does not document; they can be switched off in one place.
  4. Unknown is not zero. A process whose statistics macOS withholds shows "—", not 0 %. The first sample after sleep has no rate rather than one giant rate.
  5. A monitor must be light. One sampling loop, tiered intervals, buffered writes, and its own CPU and memory are measured and shown like any other process (§26).
  6. Nothing leaves the Mac. No telemetry, no advertising, no update check. See §27.

# 3. Application preview

Dashboard, Dark Mode
Dark Mode — the Overview layout.
Dashboard, Light Mode
Light Mode — same layout, text colours tuned to at least 4.5:1 contrast.
CPU page, Dark Mode
CPU, Dark Mode.
CPU page, Light Mode
CPU, Light Mode.
Performance dashboard preset
The built-in Performance layout.
Dashboard in French (Canada)
Français (Canada), with locale-aware numbers and units.

Screenshots are produced by Scripts/screenshots.sh from an isolated instance of the signed Release app. The privacy mask is on, so addresses, host and user names appear as "•••". How each image was made, and the two that are not window captures, is stated in docs/screenshots/README.md.

# 4. System dashboard

System dashboard
  • 14 widgets: CPU, CPU cores, GPU, memory, storage, disk activity, network, battery, thermal state, top processes by CPU, top processes by memory, system (uptime, process count, load), alerts, ORIX Monitor's own overhead.
  • Customisable: Edit shows controls to add, remove, resize (small, wide, full width) and reorder widgets, by menu or by drag and drop.
  • Layouts: three built-in presets (Overview, Performance, Compact), "Save Layout As…", reset to default, delete.
  • Several displays: Monitor › New Dashboard Window (⇧⌘D) opens any layout in its own window.
  • The grid reflows from four columns to one as the window narrows.

# 5. CPU monitoring

CPU page: total usage, user and system time, per-core bars, core activity heatmap
Metric Source Notes
Total, user, system, idle host_processor_info(PROCESSOR_CPU_LOAD_INFO) Tick deltas summed over all cores; 100 % = every core busy
Per-core usage same Bars and a core × time heatmap of the live window
Load average (1, 5, 15 min) getloadavg As reported
Peak and average of the live window derived Last 150 samples
Sampling interval measured Configured interval and the interval actually measured for the last sample
Process contribution proc_pid_rusage 100 % = one core, as in Activity Monitor
Core groups sysctl hw.perflevelN Count per performance level ("6 Super · 12 Performance" on an M5 Max)

Cores are shown by number, unlabelled: macOS publishes how many cores each performance level has, not which core index belongs to which level, so ORIX Monitor does not guess. CPU frequency is not published on Apple Silicon and is listed as unavailable. Details: docs/metrics/cpu.md.

# 6. GPU monitoring

GPU page: best-effort utilization, explanation of the figure, Metal device capabilities

macOS has no supported API for system-wide GPU utilization. ORIX Monitor therefore splits the page in two:

  • Documented (Metal): device name, unified memory, recommended working set, largest buffer, ray tracing support, low-power / removable / headless flags.
  • Best effort (IORegistry): device, renderer and tiler utilization, GPU core count and driver memory figures, read with a public IOKit call from the IOAccelerator service's PerformanceStatistics property — a name Apple does not document. The values are shown exactly as published, carry a "Best effort" badge everywhere, and disappear when Settings › Sampling › Read undocumented system properties is off.

Per-process GPU usage, GPU temperature and GPU power are listed as not available. Details: docs/metrics/gpu.md.

# 7. Memory monitoring

Memory page, Dark Mode Memory page, Light Mode
Term What ORIX Monitor shows
Physical memory Installed RAM (hw.memsize). Used + cached files + free always equals it
Used App memory + wired + compressed (Activity Monitor's convention)
App memory (internal − purgeable pages) × page size
Compressed RAM occupied by the compressor — not the size of the data before compression
Cached files File-backed and purgeable memory the system can reclaim
Pressure The kernel's own level: normal, warning, critical
Swap Used and allocated (vm.swapusage); it is disk space, not part of physical memory
Paging Page-ins, page-outs, swap-ins, swap-outs per second
Virtual memory Deliberately not shown: reserved address space says nothing about RAM in use

Details and formulas: docs/metrics/memory.md.

# 8. Disk monitoring

Disk page: volumes, throughput, available-space trend, block devices
  • Volumes (logical): name, format, capacity, space available including what macOS can purge, space free without purging, startup / read-only / removable tags, BSD name and the container it lives in.
  • Block devices (physical): model, connection, size, read and write throughput, totals since boot, from IOBlockStorageDriver statistics. Disk images are listed but excluded from totals, since their I/O already appears on the device that holds them.
  • Trend of available space on the startup volume, which also feeds the "volume is filling up" finding.
  • Not shown: SSD health, wear and temperature. NVMe SMART data is reachable only through privileged or private interfaces, so ORIX Monitor shows none.

Details: docs/metrics/disk.md.

# 9. Network monitoring

Network page: throughput, Wi-Fi link, DNS and routing, interfaces
  • Throughput from 64-bit interface counters (sysctl NET_RT_IFLIST2). Totals add Wi-Fi, Ethernet and cellular; VPN tunnels are listed but not added, because their traffic already crosses one of those links.
  • Interfaces: Wi-Fi, Ethernet, VPN / tunnel, bridge, loopback and others, with status, addresses, rates, totals, errors.
  • Wi-Fi link: RSSI, noise, signal-to-noise, link rate, channel, band, PHY mode (CoreWLAN). The network name is not read: it requires Location Services, which ORIX Monitor never requests.
  • DNS and routing: primary interface, router, DNS servers, search domains (SystemConfiguration).
  • Latency test: five TCP handshakes to a host you type, only when you press the button. It is the only network traffic the app ever creates.
  • Change log: connected / disconnected events from NWPathMonitor.
  • Not shown: per-process traffic. It needs a network extension or a private framework; ORIX Monitor intercepts nothing.

Details: docs/metrics/network.md.

# 10. Process explorer

Process explorer: sortable table with CPU, memory, threads, CPU time, power, and the inspector
  • Sortable table: name, PID, CPU, memory (physical footprint), threads, CPU time, power, user, start time.
  • Filters (my processes, apps, other users, all) and search by name, PID or path.
  • Inspector for the selected process with a live CPU and memory history kept only while it is selected, disk bytes read and written, parent process and executable path.
  • Actions: Reveal in Finder, Bring to Front, Copy PID, Quit… and Force Quit… — only for your own processes, always behind a confirmation that names the process and explains the consequence. ORIX Monitor never ends a process on its own.
  • Processes of other users (root and system accounts) are listed with their identity only. macOS refuses their statistics to an unprivileged app, and ORIX Monitor installs no privileged helper to get around that.

# 11. Power and battery

Power page: battery charge, health, power flow, energy by process
Value Source Label
Charge, charging state, power source IOKit power sources Measured
Time remaining / until full IOKit power sources Estimate (the system's own)
Low Power Mode ProcessInfo Measured
Adapter wattage IOPSCopyExternalPowerAdapterDetails Measured
Cycle count, full-charge and design capacity AppleSmartBattery registry entry Best effort
Battery flow (V × A), system load same Best effort
Power by process kernel energy accounting (ri_billed_energy) An accounting figure for comparing processes

Battery flow is the power entering or leaving the battery, not what the Mac draws from the wall. Desktop Macs expose no power figure through supported interfaces; on a Mac without a battery the page says so. Details: docs/metrics/power.md.

# 12. Thermal monitoring

Thermal page: thermal state, unavailable sensors, availability matrix for this Mac
  • Thermal state (nominal, fair, serious, critical) from ProcessInfo.thermalState, with its history.
  • CPU temperature, GPU temperature, fan speed: shown as "Not available through supported system interfaces." They exist only behind the System Management Controller and private sensor services, which differ between models and break between releases. ORIX Monitor does not use them.
  • Battery temperature: shown as best effort when the battery gauge publishes it. On macOS 27 on the test Mac it does not, and the page says so.
  • Availability matrix: a table, probed on this Mac at launch, of every metric with its access class and whether it could actually be read.

Details: docs/metrics/thermal.md.

# 13. Menu bar

Menu bar panel Menu bar item with CPU, memory, network, disk and battery indicators

  • Indicators: CPU, memory, network, disk activity, battery — each can be hidden. With all of them off, the ORIX pulse mark remains alone.
  • Mini charts (optional), and a dot when an alert is active.
  • Drawn as a single template image, so macOS tints it for light, dark and highlighted menu bars.
  • The panel shows live tiles, active alerts, top processes, pause / resume, and opens the full window.
  • While only the menu bar is showing, sampling drops to the slower background interval.

The capture Mac hides the status item behind its notch, so the panel above is the real panel shown in a plain window, and the item strip is the image the app draws for the menu bar, written to a file. See docs/screenshots/README.md.

# 14. Historical telemetry

History page: stored CPU usage over an hour with minimum, average, maximum, sample count and gaps
Tier Holds Default retention
Raw Every sample 6 hours
Minute Minimum, average, maximum, count per minute 14 days
Hour Same, per hour 2 years
  • Ranges from 1 hour to 1 year; the store answers from the finest tier that covers the range and downsamples to the chart width while keeping minima and maxima.
  • Compare two metrics, read any point with the pointer, export the chart as PNG or the data as CSV.
  • Gaps are shaded, never filled. History exists only while ORIX Monitor runs; sleep, pauses and quits appear as holes, and lines are not drawn across them.
  • Bookmarks mark a moment so it can be found again.
  • Retention is adjustable; history can be erased or recording turned off in Settings.

Details: docs/architecture/storage.md.

# 15. Alerts

Alerts page: active alerts, notifications and snooze, rule list, history
  • Rules on CPU, memory pressure, memory, swap, available space, disk and network throughput, battery, thermal state, GPU.
  • Each rule has a threshold, a hold time (how long the condition must last), a cooldown (how long before it may fire again) and a severity.
  • Snooze for 15 minutes, 1 hour or 8 hours; alert history; alerts in the menu bar; Notification Center only if you enable it. One sustained problem produces one alert.
  • Time spent asleep or paused never counts toward a hold time.

Details: docs/architecture/alerts.md.

# 16. Performance intelligence

Insights page: findings with their evidence, and the list of checks

Findings are computed from the last 24 hours of stored history. Each carries the metric, start, duration, threshold, peak, mean and number of samples behind it, an explanation and a suggested action.

Finding Evidence required
Sustained high CPU Average above 85 % for 10 minutes or more
Elevated memory pressure Warning or critical for 5 minutes or more
Swap growth 2 GB or more within the window
Startup volume filling up A consistent decline over at least 6 hours projecting a full volume within 30 days — labelled as an estimate
Unusual network volume Minutes far above the series' own typical level and above an absolute floor
Repeated process spikes A process holding a full core for 30 s, three times or more
Thermal pressure Serious or critical for a minute or more

A single unusual reading never produces a finding, a hole in the data ends an episode instead of extending it, and no finding claims a hardware fault.

# 17. Reports

Reports page: report type, period, export formats, comparison, preview

Seven report types (system overview, CPU, memory, storage, network, process activity, performance incident) in four formats:

Format Contains
PDF Tables plus a chart per metric with its min–max band, gaps shaded
Markdown The full report as text
CSV Every stored bucket in long format, dot decimals, ISO 8601 timestamps
JSON The complete report; two JSON reports can be compared side by side

Every report lists measurement units, collection methods, timestamps, the sampling interval, data gaps and limitations. The host name is excluded unless you opt in; reports never contain a serial number, IP addresses or user names. Details: docs/architecture/reporting.md.

# 18. Metric sources

Area Interfaces
CPU host_processor_info, getloadavg, sysctl hw.*
Memory host_statistics64(HOST_VM_INFO64), sysctl vm.swapusage, kern.memorystatus_vm_pressure_level
Disk FileManager / URLResourceValues, DiskArbitration, IOKit IOBlockStorageDriver statistics
Network sysctl NET_RT_IFLIST2, getifaddrs, SystemConfiguration, CoreWLAN, Network framework
Processes libproc: proc_listallpids, proc_pidinfo, proc_pid_rusage, proc_pidpath
Power IOKit power sources, ProcessInfo; best effort: AppleSmartBattery registry entry
Thermal ProcessInfo.thermalState
GPU Metal; best effort: IOAccelerator registry entry

No private framework, no SMC access, no kernel extension, no powermetrics, no shell command at run time. The formula of every stored metric is in docs/metrics/ and in the app at the bottom of each page.

# 19. Metric availability

Condensed from docs/research/macos-capability-matrix.md:

Class Examples What ORIX Monitor does
Public API CPU load, memory accounting, volumes, disk and network throughput, thermal state, battery charge Shows it
Estimate Time remaining, projected date a volume fills Shows it with an "Estimate" badge
Best effort GPU utilization, cycle count, capacities, battery flow, system load Shows it with a "Best effort" badge; one switch turns all of it off
Needs your permission Wi-Fi network name (Location Services) Does not ask
Needs a privileged helper CPU and memory of other users' processes Installs none; shows "—"
Not exposed CPU / GPU temperature, fan speed, SSD health, per-process network and GPU use, CPU frequency Says "Not available through supported system interfaces."

# 20. Technology stack

Layer Technology Role
Language Swift 6, strict concurrency Everything
UI SwiftUI, AppKit where needed (NSImage for the status item, NSSavePanel, Core Text for PDF) 13 pages, settings, menu bar extra
Charts SwiftUI Canvas (live charts, heatmap, sparklines), Swift Charts (stored history) Live charts redraw once per sample, with no animation
Telemetry core Swift package ORIXMonitorCore, no SwiftUI Collectors, scheduler, store, alerts, findings, reports
Storage SQLite (system library), WAL Time series and events
System Mach, libproc, IOKit, DiskArbitration, SystemConfiguration, CoreWLAN, Network, Metal, UserNotifications, ServiceManagement Sources
Project XcodeGen (project.yml) The .xcodeproj is generated, not committed
Third-party code None —

Metal is used to describe GPU devices, not to draw: a few hundred points per chart do not justify a custom renderer. Live charts were first built with Swift Charts; measured on the signed app, the animation between samples cost about 10 % of a core on the CPU page, so they were rewritten on Canvas and redraw once per sample (§26).

# 21. Architecture

flowchart LR
    subgraph SYS["macOS interfaces"]
        A1["Mach host statistics"]
        A2["libproc"]
        A3["IOKit registry"]
        A4["sysctl and getifaddrs"]
        A5["ProcessInfo, CoreWLAN, Metal"]
    end
    subgraph CORE["ORIXMonitorCore (no SwiftUI)"]
        C["Collectors"]
        N["Normalizer"]
        E["TelemetryEngine (actor)"]
        S[("TimeSeriesStore (SQLite)")]
        AL["AlertEngine"]
        IN["IntelligenceEngine"]
        R["ReportGenerator"]
    end
    subgraph APP["App (SwiftUI, main actor)"]
        M["MonitorModel"]
        UI["Pages and dashboard"]
        MB["Menu bar extra"]
        NO["Notification Center"]
        EX["PDF, Markdown, CSV, JSON"]
    end
    SYS --> C --> N --> E
    E -->|"values"| S
    E --> AL -->|"transitions"| S
    S --> IN
    E -->|"snapshot stream"| M
    M --> UI
    M --> MB
    AL --> NO
    S --> R --> EX
    IN --> UI

One sample, end to end:

sequenceDiagram
    participant T as TelemetryEngine
    participant C as Collectors
    participant A as AlertEngine
    participant S as TimeSeriesStore
    participant M as MonitorModel
    T->>T: effective interval (window visible, on battery, Low Power Mode)
    T->>C: sample CPU, memory, disk, network, GPU
    C-->>T: counters and rates (no rate without a baseline)
    T->>T: normalize to stored metrics
    T->>A: evaluate rules
    A-->>T: fired or resolved
    T->>S: append (buffered, flushed every 30 s)
    T-->>M: snapshot (one-slot stream)
    M->>M: update the 150-sample live window

Alert rule life cycle:

stateDiagram-v2
    [*] --> Idle
    Idle --> Holding: condition true
    Holding --> Idle: condition false or gap in sampling
    Holding --> Firing: held long enough, cooled down, not snoozed
    Firing --> Idle: condition false (resolved)

More diagrams and the reasoning behind each choice: overview · telemetry · collectors · storage · alerts · reporting.

Repository layout

text
ORIXMonitor/
├── App/Sources/
│   ├── App/            entry point, MonitorModel, settings
│   ├── DesignSystem/   tokens, components
│   ├── Features/       dashboard, hardware pages, processes, history, analysis, reports, settings, menu bar
│   └── Reporting/      PDF renderer
├── App/Resources/      asset catalogue (icon, accent), string catalogue (en, fr-CA)
├── Packages/ORIXMonitorCore/
│   ├── Sources/ORIXMonitorCore/   Metrics, Collectors, Scheduler, Storage, Analysis, Reporting
│   ├── Sources/orix-probe/        command-line probe and micro-benchmarks
│   └── Tests/                     81 tests
├── UITests/            end-to-end interface tests
├── Scripts/            build, sign, notarize, package, release, bench, screenshots, localize, check
├── design/icon/        icon concepts and master artwork
├── docs/               research, architecture, metrics, design, development, release, reports, screenshots
└── project.yml         XcodeGen definition

# 22. Installation

Requirements: a Mac with Apple Silicon and macOS 15 or later.

  1. Download ORIX-Monitor-1.0.0.dmg and open it.
  2. Drag ORIX Monitor to Applications.
  3. Open it. It appears in the Dock and in the menu bar; closing the window leaves the menu bar item running.

The disk image and the app are signed with a Developer ID and notarized by Apple, so Gatekeeper opens them without a warning. Verify a download with:

bash
shasum -a 256 ORIX-Monitor-1.0.0.dmg     # compare with the value in §31
spctl --assess --type open --context context:primary-signature -v ORIX-Monitor-1.0.0.dmg

ORIX Monitor asks for no permission at launch. To uninstall, quit it and delete the app; its data is in ~/Library/Application Support/ORIX Monitor/ and its preferences under ai.spboucher.orix.monitor.

Published on 2026-11-21. The downloads were fetched back from the forge and matched the checksums in §31.

# 23. Build instructions

bash
brew install xcodegen create-dmg          # Xcode 16 or later is required
Scripts/build.sh debug                    # generate the project, build Debug
Scripts/build.sh test                     # core test suite (swift test)
Scripts/build.sh uitest                   # interface tests (drives the real app; needs the screen)
Scripts/build.sh release                  # Release build, signed with the Developer ID identity in the keychain
Scripts/release.sh                        # tests, build, signature check, notarization, DMG, ZIP, checksums, Gatekeeper

Other tools: Scripts/bench.sh (overhead), Scripts/screenshots.sh, Scripts/localize.py (string catalogue), Scripts/check.sh (author headers and secret scan), swift run orix-probe (prints one reading of every collector). Setup details and launch arguments: docs/development/setup.md.

# 24. Testing

Suite Count Result on 2026-11-21 What it covers
Core (swift test) 81 tests, 16 suites 81 passed Tick and counter arithmetic with wraparound and resets, memory accounting, disk and network rates, process CPU and the Mach time conversion (checked against getrusage), battery registry layouts, scheduler intervals, store tiers, downsampling, gaps, retention, relaunch, alert state machine, detectors, findings, report renderers, and the real collectors and engine on the test Mac
Interface (XCUITest) 13 tests 12 passed, 1 skipped First launch, every page, unavailable sensors declared, dashboard editing, process explorer, alert rule and snooze, report preview, settings, appearance, window resizing, the narrow-window regression, history across relaunch
Accessibility audit 12 pages recorded, see §28 Apple's performAccessibilityAudit on every page

The skipped test clicks the menu bar item; the test Mac hides that item behind its notch, so the test verifies that the item exists and carries live readings, then skips the click. The panel behind it has therefore not been exercised by an automated click.

The interface tests found a real crash before release: on the Processes page a narrow window sent SwiftUI's split view into a constraint loop that aborted the app. It was fixed and is now covered by testProcessesPageSurvivesANarrowWindow.

Per-test descriptions: docs/development/testing.md.

# 25. Benchmarks

Measured on the test Mac with swift run -c release orix-probe --bench (Mac17,6, Apple M5 Max, macOS 27.0), while other work was running on the machine. Median of repeated calls.

Operation Median 95th percentile Calls
CPU sample (all cores) 0.005 ms 0.008 ms 200
Memory sample 0.006 ms 0.007 ms 200
Disk activity (block devices) 0.13 ms 0.15 ms 100
Power and battery 0.37 ms 0.44 ms 50
GPU statistics (best effort) 0.78 ms 0.87 ms 100
Network interfaces and addresses 1.02 ms 1.22 ms 100
Volumes (every 30 s in the app) 16.4 ms 19.7 ms 30
Process table, 5,007 processes 22.3 ms 39.7 ms 20
Store operation (in-memory database) Result
Ingest one simulated day: 43,200 ticks × 27 metrics = 1,166,400 values, flushed every 15 ticks 1.22 s in total, 28 µs per tick
Query 1 hour of raw samples, downsampled to 450 points 0.29 ms
Query 24 hours from the minute tier, 480 points 0.32 ms
Query 24 hours from the hour tier, 24 points 0.06 ms

The process table is by far the most expensive collector, which is why it is sampled half as often as the rest. The test Mac was running about 5,000 processes at the time (simulators and builds); a typical Mac runs several hundred.

# 26. Performance overhead

Scripts/bench.sh starts an isolated instance of the signed Release app, lets it settle for 10 s, measures it for the stated time, and reads two independent sources: ps / footprint from outside, and the app's own self.cpu / self.memory metrics from its database.

Page shown Sampling interval Measured for CPU, share of one core (ps) CPU, self-reported (avg / max) Footprint at the end (footprint) Footprint, self-reported (avg / max)
Dashboard 5 s 90 s 0.87 % 0.85 % / 1.58 % 269 MB 102 MB / 246 MB
Dashboard 2 s (default) 120 s 2.32 % 2.32 % / 5.86 % 80 MB 82 MB / 248 MB
CPU 2 s (default) 90 s 2.47 % 2.42 % / 5.01 % 240 MB 90 MB / 240 MB
Processes (Apps filter) 2 s (default) 90 s 2.14 % 2.18 % / 5.02 % 63 MB 72 MB / 75 MB
CPU 1 s 90 s 4.13 % 4.26 % / 8.17 % 254 MB 243 MB / 255 MB

Conditions: signed Release build 1.0.0 (1), MacBook Pro Mac17,6 (M5 Max, 18 cores), macOS 27.0, on AC power, window on screen, while other builds and simulators were running on the same Mac (about 5,000 processes), which raises the cost of the process table. One run per row; these are single measurements, not averages over several runs.

  • CPU. Roughly 2.1–2.5 % of one core at the default 2 s interval, under 1 % at 5 s, about 4 % at 1 s. On an 18-core Mac, 2.3 % of one core is about 0.13 % of total capacity. The two methods agree to within 0.15 points.
  • Memory. The footprint is not steady: it moves between about 60 MB and about 270 MB during a run. A breakdown with footprint taken at a high point shows about 185 MB of graphics memory owned by the window's layers and about 41 MB of heap; the graphics part is allocated and released by the system and was seen falling back to under 80 MB with nothing changed in the app. Replacing Swift Charts with Canvas drawing did not change it, so it is not the charts. Its cause is not established; it is listed as an open item.
  • Disk. 1,575 samples in the 120 s run produced a 276 kB database (including its write-ahead log); writes happen once every 30 s. Extrapolated linearly, that is about 7.6 MB per hour of raw samples, capped by the 6-hour raw retention; the extrapolation is an estimate.
  • Collection time per sample is shown live in Settings › About; the collectors themselves are timed in §25.
  • A defect found by this benchmark and fixed before release: with Swift Charts animating between samples, the CPU page at 1 s measured 10.1 % of one core. Live charts now redraw once per sample on a Canvas; the same measurement is 4.1 %.
  • Not measured: energy impact, the menu-bar-only state (window closed), and behaviour on battery (where the default interval doubles).

What keeps it low: one sampling loop; process table sampled half as often as the fast tier; volumes and battery every 30 s; writes buffered and flushed every 30 s in one transaction; a one-slot snapshot stream so the interface never queues stale samples; a 150-sample live window; a slower interval when only the menu bar is showing; half the rate on battery and in Low Power Mode. Energy impact was not measured: it needs powermetrics (root) or Instruments, neither of which was run. Method and design notes: docs/development/performance.md.

# 27. Privacy

  • Local only. Measurements, history, alerts and reports stay in ~/Library/Application Support/ORIX Monitor/.
  • No account, no analytics, no advertising, no update check, no third-party code.
  • One network action, on demand: the latency test, to the host you type, when you press the button.
  • No permission requested, except Notification Center if you enable alerts there. No Location Services, no Full Disk Access, no Accessibility, no administrator password, no privileged helper.
  • Not sandboxed, because the sandbox blocks the process table and registry statistics the app exists to show; it carries no entitlement at all.
  • Privacy mask: one switch replaces addresses, host and user names by "•••" for screenshots and screen sharing.
  • Reports leave out the host name unless you opt in, and never contain a serial number, addresses or user names.

# 28. Accessibility

  • VoiceOver: every chart exposes a text summary (latest value, minimum and maximum per series); per-core bars read each core's value; rows combine label and value; page headers are headers.
  • Never colour alone: severity, pressure, thermal state and data quality always carry a word and a symbol.
  • Contrast: text colour tokens are computed to reach at least 4.5:1 on every background in both appearances. Apple's automated audit still reports contrast notes it does not attribute to an element; they are unresolved (see the report).
  • Colour-blind-safe palette: an Okabe–Ito based option for chart colours.
  • Reduce Motion: readout and dashboard animations are disabled when the system setting is on; live charts never animate.
  • Keyboard: standard navigation, ⇧⌘P pause, ⇧⌘B bookmark, ⇧⌘R refresh insights, ⇧⌘D new dashboard window.
  • Density: compact, regular, comfortable.

Apple's automated audit was run on all twelve pages; its raw output and a reading of it are in docs/reports/accessibility.md. No person has reviewed the app with VoiceOver, and macOS has no Dynamic Type; text does not scale beyond the density setting.

# 29. Localization

English and Français (Canada), 747 strings, in a string catalogue rebuilt by Scripts/localize.py from compiler-extracted keys, run-time keys and Scripts/translations-fr-CA.json. Numbers, percentages, byte counts, durations and dates follow the system locale (52,5 %, 39,9 Go). The French text was machine-translated and spot-checked; it has not been proofread by a French-speaking reviewer, and only the dashboard and history pages were looked at in French.

# 30. Roadmap

Not implemented in 1.0.0, in rough order of value:

  • Automatic updates (Sparkle was evaluated and deliberately left out until a signed release feed exists).
  • An editor for the insight thresholds (they are fixed defaults today).
  • Per-core history in the store (per-core data is live only).
  • An Intel build, once it can be tested on an Intel Mac.
  • A4 paper for PDF reports; scheduled reports.
  • A widget or Control Center presence.

# 31. Release status

Item Value
Version 1.0.0 (build 1)
Minimum macOS 15.0
Architecture arm64 (Apple Silicon)
Signature Developer ID Application: Simon-Pierre Boucher (3YM54G49SN), Hardened Runtime, secure timestamp, no entitlements
Notarization — app Accepted, submission 4f0026aa-6755-471b-9392-b06671e90083
Notarization — disk image Accepted, submission 13bf43c8-e0e8-4c84-acfc-8e74bc3f6f23
Stapled App and DMG
Gatekeeper accepted, source = Notarized Developer ID (app and DMG)
ORIX-Monitor-1.0.0.dmg 3,455,660 bytes · SHA-256 76ae76570e2c7654cdf377922bc85967d04eb20eedeaabd7675791f5b84e3be2
ORIX-Monitor-1.0.0.zip 2,515,813 bytes · SHA-256 3b91a67ff51dd880bc1250491b1abc6591a95349717318139571023bcf1ad752
Source repository Public, https://git.spboucher.ai/orix-monitor
Release https://git.spboucher.ai/orix-monitor/releases, tag v1.0.0, published 2026-11-21
Downloads DMG · ZIP · SHA256SUMS.txt · Release notes

The repository started private, as the brief required, and was made public with its release on 2026-11-21 at the owner's request. After upload, the DMG and ZIP were downloaded from the public URLs: sizes and SHA-256 matched, the stapled ticket validated and Gatekeeper accepted the downloaded disk image. Full evidence: RELEASE-REPORT.md.

# 32. Known limitations

  • Tested hardware: developed and fully tested on one MacBook Pro (M5 Max, macOS 27.0). The notarized DMG was also installed and run for 45 seconds on an M4 Mac mini (macOS 26.7) and an M2 Mac mini (macOS 26.5.1), where it passed Gatekeeper and collected metrics. macOS 15 itself, Intel Macs, external GPUs and Macs with several batteries or a UPS were not tested.
  • No temperatures, no fan speeds, no SSD health, no per-process network or GPU usage — by design, see §19.
  • Other users' processes show identity only.
  • Best-effort values can vanish with a system update; the app is built to show "—" when they do, and that path is covered by tests on synthetic data only.
  • History has holes whenever the app is not running, and a crash or force quit can lose up to 30 seconds of samples.
  • Menu bar item: on a Mac whose menu bar is full, macOS hides it; the app cannot prevent that.
  • Multi-display: detached dashboard windows exist, but were not tried on a second physical display.
  • Sleep and wake: handled in code and covered by engine tests with simulated time; a real sleep cycle was not part of the automated runs.
  • Notifications: the permission prompt and delivery were not exercised by the automated tests.
  • Energy impact of the app was not measured.

# 33. ORIX ecosystem

ORIX is a family of premium Apple utilities that share a design language, work without an account and keep their processing on the device.

App Platform Purpose
ORIX Scan iOS, iPadOS Document scanning, on-device OCR, searchable PDF
ORIX Calc iOS, iPadOS Universal calculator
ORIX Audio iOS, iPadOS Recorder, analysis, on-device transcription
ORIX Secure · ORIX Camera iOS, iPadOS In development
ORIX Monitor macOS System monitoring, diagnostics and performance intelligence

ORIX Monitor reuses the family palette (canvas, surfaces, text roles, semantic colours) and brings its own accent, the cyan pulse. It shares no code and has no run-time dependency on the other apps. See docs/design/brand-guidelines.md and docs/design/icon-design.md.

The five icon concepts, each shown at 128, 64, 32 and 16 pixels
The five icon concepts explored; the first, the ORIX "O" crossed by a pulse, was chosen.

# Author

Simon-Pierre Boucher — www.spboucher.ai · contact@spboucher.ai

# 34. License

All rights reserved © 2026 Simon-Pierre Boucher. See LICENSE.

Clone orix-monitor

Anonymous clone and fetch. Pushing requires the owner's personal access token.

Snapshot of main

Files main
Menu

Theme