Most of the software you touch in a day is really a request sent to someone else's computer. Your documents live there. Your notes live there. The thing that represents you, more often than not, lives there too. It's convenient, and it's the default, and it asks you to forget a simple question: what happens to all of this the day the server goes away, changes its terms, or decides you're no longer a customer?
There's a quieter future taking shape underneath the loud one. Call it digital self-sufficiency: the practice of keeping your important tools on hardware you own, running whether or not anyone's connection is up, answerable to you and no one else.
Offline is a feature, not a limitation
For years "offline" meant degraded, the sad grey screen you saw when the WiFi dropped. That framing was always backwards. A tool that works offline is a tool that works, full stop, with no dependency on a company's uptime, pricing, or continued existence. It can't be revoked. It can't quietly change what it does overnight. The bytes never leave the room.
Local-first software makes a few things true that the cloud model simply can't match:
- There's nothing to breach. A machine that never uploads your data can't leak it.
- There's no landlord. You're not renting access to your own work.
- It keeps working. No connection, no subscription lapse, no sunset announcement can take it from you.
The new leverage: vibecoding and agent engineering
Here's what's changed, and why self-sufficiency is suddenly practical rather than nostalgic. Building software used to require a team. Now a single person with a clear idea can vibecode a working tool in an afternoon, describing what they want in plain language and shaping it as it takes form. Push that further and you get agent engineering: composing autonomous agents that research, write, and wire together the small programs you need, so the tool bends to you instead of the other way around.
The frontier moves fast enough that keeping track of it is its own discipline. That's what Gerolamo is for, a competitive-intelligence engine that watches where the technology is actually heading, so the people building tools can build the right ones. When you can survey the landscape and then assemble what you need from it, self-sufficiency stops being a sacrifice. You give up nothing and keep everything.
An older idea, wearing new clothes
None of this is really new. The most self-sufficient tool ever made is a notebook. It needs no account, syncs with nothing, and answers only to the person holding the pen. The Progoff Intensive Journal method has understood this for decades: reflection is most honest when it's private, unmonitored, and kept entirely by you. A journal is offline software that happens to be made of paper.
Digital self-sufficiency is just that instinct, extended to the tools we now live inside. The workshop where we build in that spirit is Adjective, and the projects that come out of it share one rule: the important thing stays with you.
Which brings us to Inksign
A signature is the most personal mark you make. It stands in for your consent, your identity, your word. So it's strange that the standard way to sign a document today is to upload it to a stranger's server and let a key you'll never see apply the mark on your behalf.
Inksign takes the opposite stance, on purpose. Your signing key never leaves your machine. It runs offline. It produces a real, standards-based PAdES signature that anyone, anywhere, can verify without trusting us, or a server, or a connection. It's a small tool that does exactly what it says, on hardware you control.
That's what digital self-sufficiency looks like in practice. Not a retreat from the future, but a claim on it: the tools that matter most should live where you do.