Why we chose local-first over SaaS

The question we hear most from investors

“Why don’t you just build it as a SaaS?”

It’s a fair question. A cloud platform would be easier to deploy, easier to update, easier to monitor. We could onboard a thousand users in a week instead of a month. We wouldn’t need to worry about ARM compatibility, local SQLite databases, or mDNS resolution.

We chose the harder path. Here’s why.

What SaaS means when money is involved

SaaS — Software as a Service — means your software runs on someone else’s computers. For a note-taking app, that’s fine. For a photo editor, that’s convenient. For software that has your exchange API keys and places orders on your behalf, it means something different.

It means:

Your credentials live on our servers. We’d need to store your exchange API keys. Encrypted, sure. But they’d be there — one breach, one rogue employee, one court order away from exposure.
Your trading data lives on our servers. Every decision, every position, every balance. We’d know exactly how much crypto you own, what your cost basis is, and when you’re likely to sell. That’s a goldmine for anyone who wants it.
We become a single point of failure. If our cloud goes down at 3 AM during a crash, none of your strategies execute. If we get DDoS’d, hacked, or simply make a deployment mistake, your money sits idle — or worse, orders get duplicated.
We can change the rules without you noticing. A SaaS platform can push updates silently. The evaluation logic that ran your strategy yesterday might be different today. You’d never know unless you were watching the network requests.

None of these are hypothetical risks. They’re the standard operating reality of every cloud-hosted trading platform.

What local-first means

Aurono runs on a device you control. A small machine on your home network — always on, always yours.

Your credentials never leave your network. Exchange API keys are encrypted on the device itself. They’re never transmitted to us, never stored on our servers, never visible to our team.
Your data stays home. Every event, every ledger entry, every portfolio snapshot exists only on your device. We can’t see it. We can’t sell it. We can’t lose it in a breach.
You don’t depend on us. If Aurono Labs disappears tomorrow — goes bankrupt, gets acquired, loses interest — your device keeps running. Your strategies keep evaluating. Your trades keep executing. Nothing changes.
Updates are explicit. You choose when to update. You can inspect what changed before installing. There are no silent pushes, no forced migrations, no “we changed the terms of service."

"But it doesn’t scale”

True. And that’s the point.

SaaS scales horizontally — one server, a thousand users. Local-first scales linearly — each user runs their own instance. From a venture capital perspective, that’s inefficient.

But from a trust perspective, it’s the only architecture that works.

When software handles money, the relationship between user and software must be direct. Not mediated by a company’s infrastructure. Not dependent on a company’s continued existence. Not subject to a company’s business pressures.

Every cloud-hosted trading bot that has shut down, been hacked, or changed its terms has proven this point. The users who were fine were the ones who had their own systems.

The tradeoffs we accept

We’re not naive about the downsides of local-first:

Harder onboarding. Setting up a local device takes more effort than clicking “Sign up.” We accept this because the alternative is holding your keys on our servers.

Slower feature rollout. Users need to update manually. We accept this because the alternative is pushing untested code to systems that trade real money.

More support complexity. We can’t SSH into your device to debug. We accept this because the alternative is having remote access to a machine that holds your exchange credentials.

No network effects. We can’t aggregate data across users to build “smart” features. We accept this because aggregating trading data is the exact kind of incentive misalignment we’re trying to avoid.

Every tradeoff comes back to the same principle: we’d rather be limited than compromised.

What we kept from SaaS thinking

Local-first doesn’t mean primitive. We kept the parts of modern software design that make sense:

Automatic updates available — you choose when to install them, but they’re easy.
Email reports — your device sends you daily and weekly summaries. You don’t need to check the dashboard.
Web interface — Aurono has a full browser-based UI, accessible from any device on your network. It feels like a web app. It just happens to run in your house.
Event-sourced architecture — every decision is logged as an immutable event. You get the auditability of a cloud system without the cloud.

The real question

The question isn’t “why not SaaS?” The question is: who should be in control of software that moves your money?

If the answer is “the user,” then the software has to run on the user’s device. That’s not a technical limitation. It’s a design principle.

Cloud platforms are great for collaboration, for social features, for anything that benefits from centralization. Trading execution isn’t one of those things. Your strategy is personal. Your capital is personal. Your risk tolerance is personal. The software that executes all of this should be personal too.

The bet we’re making

We’re betting that a growing number of people will choose control over convenience. That they’ll prefer a system they own over a system they rent. That they’ll value the peace of mind of knowing their trading infrastructure doesn’t depend on a startup’s runway.

It’s a slower path. It’s a harder path. But it’s the right one for software that handles money.

Aurono runs on your device, on your network, under your control. That’s not a limitation — it’s the whole point.

Try Aurono for free in shadow mode — €99 license unlocks live trading.