The MNT Pocket Reform is an okay system, if you're okay with its compromises. Every product is a package of emphasis, and the Pocket Reform is a more extreme package than most: MNT spent nearly everything on a few things they care about deeply and very little on several things most laptops treat as the baseline. Which of those matter to you decides whether this is a lovely little computer or an expensive puzzle box. As usual, the opinions are at the end.
What it is
The Pocket Reform is a 7-inch Linux laptop from MNT Research in Berlin. It was crowdfunded on Crowd Supply in March 2023 at $899 for the base black model, started shipping in June 2024, and now sells from MNT's own shop for upwards of €1,000 depending on configuration. It has a CNC-milled, bead-blasted aluminium shell, a 1920x1200 display, a 60-key mechanical keyboard on Kailh Choc switches with per-key RGB backlighting, a tiny optical trackball with four buttons, a small OLED status screen built into the keyboard, a mono speaker, a 3.5mm headset jack, two USB-C ports, Micro HDMI, a microSD slot, an M.2 slot for an NVMe drive, and a processor module you can swap out.
The original module was an NXP i.MX8M Plus with four Cortex-A53 cores. Mine has the newer RCORE RK3588, which has four Cortex-A76 cores and four A55s; MNT also sell it as a €430 upgrade for people who bought the old one. I've put a 1TB NVMe drive in mine. It runs Debian, with GNOME as the default desktop. It weighs about 1.1kg and measures 20 by 12.6 by 4.5cm.
What MNT emphasised
Ownership
Everything about the Pocket Reform is built around the idea that the machine belongs to you. Every board is documented and the schematics are online. The keyboard firmware is open source and builds on the machine itself. The batteries are ordinary LiPo cells you can buy and replace. The processor lives on a module, so when something faster arrives you swap a board instead of buying a laptop. It comes apart with one screwdriver. This is the core of the package, and MNT have delivered it more completely than almost anyone else selling a computer.
The typing experience
MNT put a real mechanical keyboard, on proper low-profile switches with real travel, into a 7-inch machine. Nobody else does that. You choose the switches when you order: clicky Kailh Choc Whites or linear Choc Pro Reds. I picked the Whites, thinking I'd like them, and I don't. They click loudly, and typing on them sounds like I'm wearing plastic nails. That's on me, not MNT. They offered the choice and I chose wrong. They also chose an ortholinear layout, every key in a strict grid of twelve per row, because they believe it's better ergonomically, and the people who already use Plancks and Kinesis Advantages tend to agree. The keyboard is so central to the product that MNT now sell it on its own as a standalone keyboard.
Durability
The shell is milled aluminium on solid metal hinges, and the whole thing is dense. It feels like it would survive being run over. You don't baby it.
Connectivity in a small footprint
Two USB-C ports, Micro HDMI, microSD, an M.2 slot, an optional cellular modem, and a headset jack on the left side, all in a 20 by 12.6cm footprint. For a machine this size, that's a generous set of ports.
Performance, with the right module
With the RK3588, it boots from NVMe to a talking desktop in about eleven seconds. Orca is responsive, GNOME doesn't drag, and it builds software comfortably, keyboard firmware included.
Listening to its users
Since MNT's September 2025 system images, the Pocket Reform says "Welcome. Press Super Alt S for screenreader" at boot, and Super+Alt+S starts Orca. That exists because I sent MNT a DM one day asking about it, and they did the work. I don't know whether MNT have any other blind users. They might, they might not. Either way, they made those changes for one person who asked. They also ship overrides that let root run PipeWire, which is exactly what a console screen reader like Fenrir needs to get speech out without a graphical session. Somebody at MNT thought about that. Most hardware companies many times their size have never bothered with either.
What MNT deemphasised
Keyboard conventions
The grid is only the start. Caps Lock doesn't exist: MNT put a Control key in its place because "many advanced users remap the traditional Caps Lock key to a different function" anyway. Insert doesn't exist either. The function row doesn't exist. F1 to F10 live on the number row behind a Hyper key, F11 and F12 are Hyper+Q and Hyper+W, and Home, End, Page Up and Page Down are Hyper plus the arrows. Square brackets are Hyper+O and Hyper+P, curly braces add Shift on top, and backtick and tilde are on Hyper+Escape. The number row keys aren't engraved with their shifted symbols because MNT "didn't want the keys to look cramped".
The Hyper key is handled entirely inside the keyboard's firmware, and the operating system never sees it. You can't remap it with xkb or bind it in GNOME. Changing it means rebuilding and flashing the firmware on the RP2040 microcontroller inside the keyboard. Hyper is also the power button: hold Hyper+Enter for about two seconds, or tap Hyper+Enter and press 1.
The remaining keys are spent in odd places. Row by row, the stock layout is:
- Escape, 1 to 0, Backspace
- Tab, Q to P, semicolon
- Control, A to L, apostrophe, Enter
- Shift, Z to full stop, Up, Right Alt
- Hyper, Super, Alt, equals, Space, Space, minus, slash, Left, Down, Right
Two space keys, on a keyboard with no room for Insert. Apostrophe under the right pinky on the home row. The up arrow exactly where your hand expects the forward slash, and the slash moved down to the bottom row between minus and the left arrow. Equals and minus nowhere near where twenty years of muscle memory put them.
Tactile landmarks
There are no identifying marks on any key. Not on F, not on J, not anywhere. Someone on MNT's own forum has already asked for bumps on F and J on a future model. On an ortholinear grid, where every key is the same size and sits directly above and below its neighbours, the stagger that normally gives your hands a shape to feel is gone too. Every row is a strip of identical squares.
Sleep
There isn't any. MNT deliberately disable suspend and hibernate, because they don't work on the RK3588. On the older i.MX8M Plus, suspend worked when the machine first shipped, then regressed in a kernel update and was never fixed.
Battery life
Measured from the battery's own current and voltage, mine idles at around 9W with the backlight off, which in practice is two to three hours from a pack of roughly 30Wh. The internal Wi-Fi takes about 1.5W, the display panel about 1.4W, and the backlight at full adds another watt. With the screen fully off, idle drops to about 6W and stretches towards five hours. Most of what's left is the SoC, RAM and the NVMe drive, and MNT's kernel command line turns PCIe power management off, so a drive like mine, a no-name 1TB with a single power state, never idles at all.
Size and weight
The footprint is small. The rest isn't. 1.1kg and 4.5cm thick is heavier than plenty of 13-inch ultrabooks.
Charging feedback and battery reporting
Plugging in gives no audible or tactile sign that charging has started. The two USB-C ports on the right side feel identical, and only the top one charges. The battery status Linux reports flips between charging, discharging, not charging and full every few seconds to every few minutes, sometimes with capacity readings between zero and nineteen percent that are simply wrong, on battery as well as on the charger, alongside errors on the link to the system controller. Charging runs at a minute to a minute and a half per percent, apart from a stretch around 80 to 84 percent that crawled for no reason I could find.
Audio
One mono speaker. Turning the DAC up even half a decibel above where it sits clips against the speaker amplifier's fixed gain. It's loud enough. It isn't good.
Wireless extras
No Bluetooth. The Wi-Fi card is a MediaTek part that only does Wi-Fi, sitting on the internal USB hub.
A forgiving setup and update path
The first-run wizard only starts if /home is empty. Firmware and kernel versions have to match, and the system doesn't stop you updating one without the other. Recovery assumes you can read a screen, or at least an OLED.
Price
None of this is cheap. You're paying for low-volume manufacturing, milled aluminium, documentation and openness, and the price reflects it.
Who the emphasis serves
The buyer this package is built for wants to own their computer completely, and values open hardware enough to pay a large premium for it. They probably already type on an ortholinear keyboard, or want to. They see reflashing keyboard firmware as an afternoon's fun. They look down at the keys, read the legends, glance at the OLED for battery status, and carry a charger or a power bank because they know the battery won't last a day. Losing sleep and gaining weight is a fair trade for a machine they can repair in ten years. That buyer exists. They're on the MNT forum right now, and the Pocket Reform serves them extremely well.
Where the package logic breaks down
When the user can't see the keyboard
Every deemphasis in the keyboard assumes a sighted user. Missing legends, a missing function row and an unusual layout are mild costs if you can glance down. Without sight, they stack.
Orca's modifier is Caps Lock in laptop layout and Insert in desktop layout. The Pocket Reform has neither. So the screen reader MNT worked to make available at boot has no modifier key on the stock keyboard, and every Orca command you'd use day to day, from reading the current line to flat review to preferences, depends on a key that isn't there. A screen reader's navigation is built on modifier chords. On this keyboard, before you change anything, a large number of ordinary actions are either impossible or a two-modifier stretch through a firmware layer the OS can't see, on a grid with no landmarks.
The missing bumps hurt more than they would on any other keyboard. With no stagger and no ridges, you find your place by edge-counting from the side of the keyboard, or by pressing something and listening. Months in, I still regularly open the firmware's matrix header file, the C source that defines what every key position sends, to work out where a key is. The source code is the only place that tells you, row by row, exactly what's under your fingers. I have to read a header file to learn my own keyboard. That is the most Linux thing that has ever happened to me. I've since written the layout out as a plain text file on the desktop, with a second file of every shortcut, and I update both every time the firmware changes.
When the feedback is visual
The OLED menu is a clever idea: check your battery or power the machine on and off without booting Linux. It's also a four-line screen controlling the power to the very machine I'd need running to have anything read it to me. The same goes for charging. A sighted user sees a light or an icon. I get nothing from the hardware, and a battery level from Linux that I can't trust.
When something goes wrong
Some context first. I've had my Pocket Reform since around August 2025. I had trouble getting it working back then, life got busy, as it does, and it sat in a drawer for the best part of a year until I had time to play. So when I finally picked it back up, I ran one of MNT's reform-tools steps to switch to booting from the NVMe drive, and afterwards the machine went completely silent. I couldn't tell whether it was booting at all.
The root cause took a while to find. The keyboard and system controller firmware on my unit were from June 2025, and the kernel my system had updated to needs firmware from August 2026 or later; MNT have a note about it on their forum. With the mismatch, the SPI link to the system controller fails, Linux can't see the battery, and the audio codec never starts. No codec, no sound, no screen reader. To a sighted user that's a machine with a missing battery icon. To me it was a brick.
That mismatch is largely a product of my machine sitting untouched for a year while the software moved on without it. Buy one now and it should arrive with current firmware, so you likely won't hit this. The underlying point still stands, though: on this machine, a firmware and kernel mismatch can take out the audio silently, and there's nothing that stops you getting into that state.
Recovery meant writing MNT's RK3588 system image to an SD card on another machine, booting from it, and getting in over SSH. The RK3588's boot ROM loads its bootloader from the eMMC, or from SD if that fails, and the bootloader then looks for a system on SD, NVMe, eMMC and USB in that order, so the SD card is the way back in as long as you know that's how it works. Updating both firmwares with fwupdmgr over SSH brought the codec and battery back and dropped boot to 26 seconds. Then I wiped the NVMe and migrated the working system over with MNT's reform-migrate script, which fell over halfway because a man page cache file vanished mid-copy and rsync treated it as an error, so the second pass and the boot configuration were finished by hand. It now boots from NVMe in about 11 seconds, the old system sits untouched on the eMMC, and the SD card lives in my bag as a rescue disk.
Because I'd created my account by hand during recovery, /home wasn't empty, so the setup wizard never ran. I did everything it would have done manually: timezone, locking the root account, removing an automatic root login on the first console, setting my session, and turning Orca on at the GDM login screen and by default in every session. Without that last step, every boot ends at a silent login screen.
When audio is the interface
A mono speaker that clips is a minor gripe for most users. For a screen reader user, audio is the display, and it needed work.
Speech sent straight to the sound card through ALSA's plug device buzzed, because the plug's resampler between the synth's 22kHz output and the codec's rate is crude. The same audio through PipeWire was clean, and so was a 48kHz test tone, so speech has to go through PipeWire or a proper rate converter. Then the start of every utterance got clipped: WirePlumber suspends idle outputs after five seconds, which powers down the codec, so the first syllable of whatever Orca says next arrives while the hardware is waking up. A small WirePlumber config file now keeps the outputs open permanently, for about 0.4W. And if WirePlumber or PipeWire restarts, speech-dispatcher's audio stream dies and Orca goes silent until you kill speech-dispatcher and restart Orca. You learn that one by falling into it. The headset jack is what I actually listen through.
Making the keyboard work
I built MNT's keyboard firmware from source, on the Pocket Reform itself, against the Raspberry Pi Pico SDK, and flashed it with picotool with an external USB keyboard plugged in the whole time in case anything went wrong. On top of MNT's current firmware:
- The key in the Caps Lock position is now Insert, which gives Orca a modifier. Once Orca has a modifier, most of everything else can be worked around.
- The two bottom-row space keys are now Home and End.
- The four trackball buttons are keys instead of mouse buttons: Control and Space to the left of the ball, Space and a context menu key to the right. I don't use a pointer, and four keys under my thumbs are worth far more than a middle click.
- The Hyper layer gained media keys (P play/pause, R previous, N next, U and D for volume), Alt+F4 on Hyper+C, and a display toggle on Hyper+B. The closing square bracket moved from Hyper+P to Hyper+semicolon to make room.
Every one of those was a trade, because there are almost no spare keys. Building it also meant learning that in the firmware's own key map, the code you'd expect to mean Compose actually means Hyper, so a real context menu key has to send a different code and arrive as Compose at the other end. You only find that out by reading the source.
Making the OLED talk
The RP2040 in the keyboard has no audio. So the modified firmware sends whatever is on the OLED to Linux over USB HID feature reports, with flags for whether the menu is open and which line is highlighted, and a small service on the Linux side speaks it through speech-dispatcher. When the menu opens, I hear it. Arrowing through it reads the highlighted line. The battery and system status pages stay open until Escape, and Enter or Space rereads them. Replies from the system controller's console get the same treatment. It only works while Linux is running, because the codec has no power when the machine is off, so powering on is still done blind: hold Hyper+Enter and wait for the greeting.
The screen curtain
Hyper+B turns the backlight off, puts the panel into power saving and turns on a screen curtain. GNOME's idle dim and undim logic kept rewriting the brightness behind my back, so the service re-applies the backlight state every second while the display is meant to be off. The curtain itself is a small GNOME Shell extension I wrote. A system service darkens the display before GDM starts at boot, and the off state is saved so it survives a reboot. All that to keep a screen off I never wanted on. It saves about 2.5W.
The desktop
The ArcMenu start menu's items had no accessible names, so Orca said "Main stage" and nothing else; a patched copy now sets each item's name from its label, and that patch should go upstream. The desktop icons extension didn't move focus to an icon when the desktop became active, so Orca announced nothing until another patch fixed it. Show Desktop on Super+D was unbound. MNT's GNOME defaults made Super+Escape the only way to close a window, so Alt+F4 went back in, which is what makes Hyper+C work. The pound sign needed the altgr-intl layout and now lives on Right Alt+Shift+4. None of these are MNT's bugs exactly, but they're what you hit setting this machine up as a desktop.
When openness meets updates
The package's emphasis on ownership makes every fix above possible. Its update path quietly undoes it. fwupd won't install an unsigned keyboard firmware, and the next official keyboard update through fwupd will overwrite mine. My keyboard is a fork I maintain by hand, one routine system update away from having no Orca modifier again.
When the portability doesn't add up
The small footprint says carry me everywhere. No sleep, two to three hours of battery, 1.1kg and 4.5cm of thickness say otherwise. You either leave it on and watch it drain, or shut it down and cold boot every time you take it out. The eleven-second boot makes that bearable. I assumed the disabled suspend was an oversight and turned it back on, then found out why it was off and turned it off again.
Against a different package
I also own an 8-inch Intel N150 clamshell, one of dozens of near-identical Shenzhen mini laptops sold under a rotating cast of brand names on Amazon and Newegg, KOOSMILE, KOOTIGERS and KOOFORWAY among them, plus plenty of unbranded listings. Mine has 12GB of LPDDR5 and a 512GB SSD and retails for around $450. It weighs 0.78kg, measures roughly 19.8 by 13.8cm, and is under 2cm thick. It shipped with Windows 11, so it ran NVDA out of the box.
Next to the Pocket Reform: nearly the same footprint, less than half the thickness, about 300 grams lighter, less than half the price, and about four hours of real use against two to three. The N150 is a much weaker chip than the RK3588, and you feel it in heavy work. For a screen reader, a browser, email and a text editor, you mostly don't.
Its keyboard is strange too, and I've said so in public, with swearing. The space bar is split around an optical nub, the full stop and slash keys are cut in half, the apostrophe sits in the right Shift slot, and F-keys are Fn plus a number. But its strangeness is at the edges. The letter keys are staggered, so you can find home by feel. There's an Insert key on the top row, so NVDA has its modifier the moment it's installed. The Fn layer works the way every laptop's does, so Windows and NVDA see the keys they expect. I installed NVDA and it talked.
Then, because apparently I still like putting Linux on everything, I put Linux on it. Mine worked. Orca had its Insert key from the first boot, and nothing needed rebuilding, patching or flashing to get there. Your mileage may vary: these machines come out of a supply chain that changes parts without telling anyone, and nobody publishes drivers for them.
Its own package deemphasises everything the Pocket Reform emphasises. Build quality is whatever the factory felt like that week. No drivers are published anywhere. The Windows image it ships with comes from a supply chain I wouldn't trust with anything sensitive. It only charges from its own hardwired brick. Nobody will sell you a replacement mainboard for it in 2034, and if the hardware or firmware gets in my way, I can't change it. Both keyboards are compromised. The clamshell's are in places a screen reader barely notices. The Pocket Reform's are exactly where a screen reader lives.
What I think
I love this thing. I use it almost constantly. It's what I reach for in bed, because it's small and fanless and doesn't cook my legs or hum at me. It's what I reach for on the couch. It's what I reach for when I just feel like using a machine I own completely, and when I want to get properly into the nitty gritty of hardware, down to the microcontroller in the keyboard. It's fast, it boots in eleven seconds, it feels indestructible, it has a headset jack where I want it, and every part of it, down to the firmware in the keyboard, is mine to change. Almost every problem in this review is one I was able to fix, and on almost any other hardware I couldn't have. That's what MNT's emphasis on ownership bought me, and it's worth a lot.
It also cost a lot. It took a custom keyboard firmware, two background services, a home-made screen curtain, two patched desktop extensions, a handful of config files, a rescue SD card I now carry everywhere, and a C header file I still open to find my own keys. I'm the kind of person who'll do that, and I enjoyed a fair amount of it. I don't think most blind users should have to, and I don't think most would want to.
MNT have shown they listen, and the screen reader at boot proves it. I'd love to see bumps on F and J, an Insert key or a firmware layout built for a screen reader as an option, and a spoken or tactile charging indicator. None of those would cost the sighted buyer anything.
And if there are other blind Pocket Reform or Reform users out there, I'd love to hear from you. What did you change? What did you give up on? Did you end up reading the matrix header too?
I'm keeping mine. I'll keep using it. I can't tell another blind person to buy one. There are smaller, lighter, cheaper machines with keyboards that are only weird where it doesn't hurt, and for most blind users who want a computer that fits in a coat pocket, that's the better package. The Pocket Reform is an okay system if you're okay with its compromises. I am. Most people reading this probably shouldn't be.