Apps

Software that finally pays its makers.

For decades, every app has fought two battles: how it gets distributed, and how it stays maintained. Noolog changes both — and puts open source back in the revenue loop.

The problem

Two problems software never solved

Buy-once software didn't survive — because writing software is recurrent, not a one-off. So the industry pivoted to SaaS as a survival mechanism: a shape baked in by the network's star topology, where everything flows to a central cloud.

It worked for vendors. But it pushed open source out of the revenue process — never a first-class citizen, always the unpaid foundation under someone else's subscription.

Today's SaaS

  • Rent forever; your data lives in their cloud
  • Distribution gated by app-store landlords
  • Open source is the unpaid substrate
  • Login walls, lock-in, no ownership

Noolog

  • Apps run on hardware you own
  • Distribution over an open protocol
  • Open-source authors paid by policy
  • Zero-login, attributable, yours

1 · Distribution

Drastically simpler delivery

The Noolog desktop app is a thin client. Apps arrive over JMAP — a modern JSON-over-HTTP sync protocol (RFC 8620) built to replace clunky, chatty sync with something batched, mobile-friendly and extensible. Those same qualities make it a clean carrier for an app and its context.

One protocol carries the app and everything it needs to run.

Because the context travels with the app, the essentials are embeddable and programmable up front:

ZK identity — prove who you are, reveal nothing Payment rails — pay for real value Permissions — declared, scoped, enforced

The result: rich zero-login interaction for users, and far easier reach for developers.

Think of it as a new kind of browser — where identity, payment and permissions travel with the app.

2 · Trust

An edge app-store you can trust

Open-source apps run on private data inside trusted edge devices. Every bit of ingress and egress — and the ROI produced — is controlled and attributable. Nothing moves off the box unseen.

And no single box is an island. Each sealed device is one node in a trusted edge distributed network — a mesh of sealed nodes that each carry their own root of trust. Users reach apps and serving through the network, regionally — not through one machine or a hyperscaler. When a node runs hot, heavy jobs overflow across peers, while private data stays local and each node caches the critical load at its own edge. Access, serving and delegated compute are distributed and trusted by construction.

A hardware owner installs a CDN, giving their region faster, closer data access — and earns ROI on that service while benefiting the wider network. Users trust it because they can attest the root of trust on the signing hardware and OS.

And the store's listing policy shares revenue back to the open-source developer — so the people who write the software are paid to keep maintaining it.

Open source, finally a first-class citizen in the revenue loop.

Distribution made trivial, trust rooted in hardware, and makers paid by construction. That's an app platform worth owning — running on a machine you can hold. See how the trust is built in Why Noolog works.

Even the client

The thin client is open source too

The Noolog app itself is built in open-source Slint — a statically-typed UI toolkit that compiles to native Rust/C++ with no garbage-collected runtime and deterministic execution. The same discipline that certifies safety-critical interfaces, so the client carrying your identity, payments and permissions is inspectable, not a black box. See how it maps onto regulation.

Claim your seat → See the nodes