Market charting,
wired into your PC.
A 1 Hz recorder sits on your hardware and takes a tick every second. Fifty-two data points off the processor, the graphics card, memory, drives, the network and the wall socket. Then it hands them to a charting terminal built the way trading software is built.
- Tick rate
- 1 Hz
- Data points per tick
- 52
- Ticks a day
- 86,400
- Per data point
- 2.8 bytes
- A day of capture
- 22 MB
- Recorder CPU load
- 0.8 %
- Price
- Free
Overview
Two things that had never been put together.
Trading terminals have had decades of work poured into one problem: making a river of numbers legible. Candles, envelopes, distributions, screeners, a tape running across the top. That craft is real, and most of it has nothing to do with money. It is about reading a signal over time.
SystemChart wires that craft to a recorder sitting on your own hardware. One tick a second, fifty-two data points on every tick, kept at full resolution for as long as you want them. Nothing averaged away, nothing summarised into a five minute blur.
What comes out is a terminal for a single machine. Same instruments, same discipline, different subject. The questions turn out to be the same ones: what was normal, when did it change, and what moved with it.
The tick rate
Sixty ticks a minute. 86,400 a day. Every part of the machine read on the same beat, so a moment can be read straight down.
Data points per tick
Plus a set for every application you tag and every game you play. The full list is further down.
Captures a day
2.8 bytes a data point, packed. Choose 1, 5, 10 or 20 GB, or no limit at all and keep the lot.
Of one processor
Measured on a real machine, not estimated. The counters are already being kept by Windows and your drivers. Reading them is the whole cost.
Accounts. Servers. Uploads.
A SQLite file on your disk and a port on loopback. Diagnostics go nowhere until you press the button that sends them.
Idle, the recorder eases to a tick every five seconds and comes straight back the moment anything happens. Set it to a flat 1 Hz and it never eases at all. Games always get the full rate.
The tick rate is yours
Three idle rates, said in hertz, with the recommended one marked. Whatever you pick, a game or a busy machine still gets the full 1 Hz tick.
Or keep the lot
Each budget is labelled with how far back it reaches on your machine, at the rate you are actually writing. Choose no limit and nothing is ever dropped.
The instruments
Charts built for signals.
Candles, ribbons, distributions, ranked screeners, stacked breakdowns and heat strips. Moving averages, rate of change, dispersion, envelopes and operating zones on any line. Every chart is drawn from ticks, so zooming in goes all the way to the second rather than to whatever bucket a summary left behind.
RSI and MACD are missing on purpose. Both assume a price set by an auction. A processor at 100 per cent is not overbought. It is busy.
Everything the machine reports is a symbol you can chart: the hardware, every application you tag, every game you play. Put a frame rate against a board temperature, or one application's memory against the whole machine's, on one panel and one clock.
Read against something
A line on its own is a number with a shape. Operating zones mark where a reading left its own normal range, fixed levels mark the ones with a meaning on any machine, and time nobody captured is drawn as a break instead of a smooth ramp from bedtime to breakfast.
Ask how often, not just how much
A distribution answers the question a line cannot: how much of the range was spent up there. A ranked screener puts every part in order with its own peak marked. A heat strip lays the whole machine out as bands sharing one clock, so a moment can be read straight down.
The tape
The one part that speaks first.
Every chart in the application answers a question you already had. The tape answers one you did not: it tells you something happened. It runs under the tabs, green for a move up and red for a move down, and it is the only surface here that volunteers anything.
Each headline is a past tense statement of something measured, ranked by how far outside the ordinary it was rather than by how recently it happened. Click one and it opens onto the captured readings behind it, with the before and after figures and the exact window they came from.
Nothing on it is predicted. A quiet machine gets a quiet tape, which is the answer you want most days.
Every tick
What gets written down.
Fifty-two data points about the machine itself, plus a set for every application and a set for every game. Graphics telemetry comes off the card where the card reports it. Where the card stays quiet, vendor neutral counters take over and the rest is left blank instead of filled with a guess.
Processor 17
- load.avg / min / max
- freq.ghz
- cores.busy, cores.p, cores.e
- time.kernel, time.user
- time.dpc, time.interrupt
- ctxsw, queue, threads
Graphics 7
- load.avg
- temp.c
- power.w
- clock.core, clock.mem
- fan.pct
- vram.mb
Memory 8
- used.gb, commit.gb
- cache.gb
- faults, hardfaults
- pool.paged.gb
- pool.nonpaged.gb
Drives 6
- load.avg
- read.mbps, write.mbps
- latency.ms
- iops, queue
- free space per volume
Network 8
- rx.mbps, tx.mbps
- util.pct, link.mbps
- packets
- errors, discards
Power 6
- watts.cpu, watts.gpu
- watts.platform
- watts.psu
- load.avg at the wall
- cost at your tariff
Per application
- cpu.pct
- mem.mb
- io.mbps
- vram.mb
Per game
- fps.avg, fps.low
- frametime.ms
- frametime.worst
- gpu.busy
- stutter.pct
Frames are the exception. They are counted as the game presents them, at its rate and not the recorder's, so a session at 240 Hz is measured at 240 Hz. When data points are added they are listed in the changelog, with the version they arrived in.
Cost tracker
What this machine costs to run.
The recorder already measures watts at the wall, so the only thing standing between that and money is a number off your electricity bill. Type in what you pay per kilowatt hour and every chart of power becomes a chart of spend.
Find the rate on your bill
One number, in pence or cents per kilowatt hour. It is on every statement, usually beside the standing charge.
Put it into Settings
Running cost takes the tariff and your processor's rated power. Nothing else is needed and nothing is sent anywhere.
Read the meter
Cost per hour sits in the live ticker. The power page breaks the draw down by part, so you can see what is actually spending it.
Where the watts go
Processor, graphics card, platform and the loss in the power supply itself, and the four add up to the reading at the wall. A machine idling at 90 W and one idling at 180 W are a real difference in what you pay, and until it is charted nobody notices either.
One number, once
Set the tariff and it applies to everything already captured, not just to what happens next. A year of history becomes a year of spend the moment you type it in.
Assistant
Ask it what happened.
SystemChart answers questions about your machine through a model you choose and pay for. Your key, your account, your bill. It ships with no key of its own, which makes running a model on the same machine the easy choice rather than the awkward one.
Every number in an answer came out of a tool that measured it against your recorded ticks. The model has no other route to a figure. Under each answer sits the list of tools it ran, so you can go and check.
It can put what it is describing on screen too. Ask for twenty minutes and you get twenty minutes, because the row of ranges holds round numbers and your question hardly ever is one.
In the window, or in your own assistant
Paste an endpoint and a key and the panel opens beside your charts. A model on the same machine needs no key at all, and Ollama, LM Studio and Foundry Local are one click each.
SystemChart is also a Model Context Protocol server, so the assistant you already pay for can read this machine directly. Settings writes the whole configuration block with the real path in it, for Claude Desktop or for VS Code, and copies it on one button. Between reading about this and using it sits a paste and a restart.
Windows encrypts any key you set under your account before it goes near the disk. The window that set it never gets it back.
Answers you can check
The chips under an answer name every tool that ran to produce it. Open the same page over the same window and the same numbers come up, because they came from the same readings.
Ask about a window with no ticks in it and it says so. A reading that never moved gets named as such rather than reported as a zero, which is the difference between a steady fan and a fan that has stopped.
Put to gpt-5.4-mini through Azure AI Foundry. The reply is unedited.
Tools it ran
The 0.9527 and the 16 seconds came out of a function running over four hours of stored ticks. The model cannot round them, average them in its head, or produce a third figure, because it has no way to reach a number except through one of these tools.
What came back
Yes. Over the last 4 hours, GPU fan and GPU temperature moved together very closely: correlation 0.9527.
The fan followed temperature by 16 seconds, with the fan lagging behind the temperature.
I’m looking at an NVIDIA GeForce RTX 5090, and the graphics telemetry is reported from the card.
Twenty tools it can reach for
Summarise
- brief
- describe
- machine
- capabilities
- capture_status
Measure
- correlate
- regress
- changepoint
- trends
- changed
Look up
- history
- composition
- applications
- games
- sessions
- events
Change the view
- show_page
- set_timeframe
- add_study
- set_markup
Sixteen of these only read. The four that change something change what is on screen and stop there. None writes a tick, deletes one, or touches capture, settings or licensing. An instruction smuggled into a window title earns you a wrong answer and no wrong actions.
While you play
A frame counter, not an injected hook.
The counter is its own click through window sitting above the game. Nothing gets written into the game process, so anti-cheat has nothing to object to and antivirus has nothing to quarantine.
Ten fields to choose from and a corner to put it in. Frames get captured whether the counter is showing or not, at the game's own rate, so every session leaves a page behind with its lows, its worst frames, and how it compares to the last time you played.
Pro Free is the whole product. Pro is the workshop. Every tick, every page, every automatic explanation and all of your history are free. See what a licence adds.
Nothing you captured is ever locked away, and a page built in Pro still reads without it. Pro buys the tools for building your own views, marking up your own charts, and making the window yours.
Six colour themes
All dark, and green stays up and red stays down in every one of them. A theme changes the room the charts sit in, never what a reading says.
Graphite and Terminal complete the set. All six are one click in Settings.
| Surface | Free | Pro adds |
|---|---|---|
| Capture | Every data point, the full 1 Hz tick, every storage budget including no limit, autostart, pause and resume | Nothing. Capture is never gated. |
| History | All of it, at full resolution, for as long as you keep it | Nothing. Your readings are yours. |
| Pages | Overview, Capture, CPU, GPU, Memory, Drives, Network, Power, Machine | Pin and rename tabs, editable copies, blank pages, the chart palette, saved layouts |
| Applications and games | Attribution, tags, category pages, game and session pages, peer comparison | Nothing |
| The tape and findings | All of it, with the captured evidence under every headline | Nothing |
| Analysis | All timeframes, automatic markup, operating zones, findings, trends, what changed | Manual indicators, drawing tools, custom limits, Compare, before and after, repeated experiments |
| Frame counter | On or off, with the default counter | Corner, fields, size and plate |
| Appearance | The Terminal theme and the Redline mark | Six colour themes, and seven finishes for the window, taskbar and tray |
| Assistant | All of it. Bring your own model. | Nothing |
Pro is one payment, once, on Steam. A licence that lapses leaves every reading, every page and every theme you already chose exactly where they were.
Availability
Coming soon to Steam.
The store page is in review. It goes up the day that comes back approved, and Steam handles the install, the updates and the community from there.