Learning Center

Your machine.
Your data.
Your rules.

Nebo runs locally. Your conversations, files, and credentials never leave your laptop unless you say so.

Local-first architecture.

Your bots run on your machine. Your data is stored on your machine. The only thing that leaves is the LLM inference call — and even that uses your own API key, so there's no middleman.

If our servers went down tomorrow, your bots would keep running.

Data flow

Your machine

Bot runtime & conversations
Files, documents, context
Credentials & API keys
encrypted inference only

LLM provider

Your API key. Your terms of service.

Verification

Ed25519 Signature

Verified against publisher key

VirusTotal Scan

0 / 72 engines flagged

Compiled Binary

No source on disk — can't be modified

Signed and scanned.

Every tool in the marketplace is signed with Ed25519 by its publisher and scanned by VirusTotal before it reaches you. Nebo verifies the signature on install — if anything was tampered with, it won't run.

Only compiled binaries are allowed. No interpreted code means the AI can't read, modify, or inject into installed apps.

No phone home.

Nebo doesn't send telemetry, usage analytics, or conversation data to our servers. Your interaction with your bots is between you and the LLM you chose. We don't see it, store it, or train on it.

Privacy isn't a toggle. It's the default.

No telemetry

Zero usage data sent to our servers

No conversation logging

We never see what you say to your bots

No training on your data

Your data is yours. Period.

Want the full technical deep dive?

Our security architecture page covers all seven layers of protection, the vulnerability hardening log, and why compiled-only binaries matter.

Read the full security architecture

AI that protects you,
not the other way around.

Security shouldn't be something you have to think about. With Nebo, it's built into every layer.