nebula@atheron:/security$
// Security and data rules
Strict rules, both ways
For your data and for members' machines.
Nebula runs work on a network that includes other people's computers. That only works if the rules protect you and them. Here they are, in plain terms.
A signed, vetted catalogue
Only open models we have checked run on the network. Each is pinned by its content and signed, so a machine can prove it ran the right model and nobody can swap it.
Every shard verified
Each shard on member devices runs on at least 2 machines owned by different people. Differences are settled by an Atheron house node, and random spot checks run on our own hardware.
Private jobs stay on our hardware
A job marked private, which is every job by default, runs only on Atheron house nodes or AWS GPUs. It never reaches a member's device.
Customer containers, fenced in
Customers who bring their own container go through extra rules.
- Only businesses that passed our business check and have a card on file
- Every image scanned for malware and crypto miners before it may run, and signed by us once it passes
- A sandbox with no network and no access to the member's files
- Members opt in, and the setting is off by default
- Limits on time, memory and GPU use, with any job that breaks them stopped
Retention you choose
Inputs and results are kept for 30 days by default and then deleted. You can choose a shorter window, or up to 90 days.
Encrypted
TLS on every connection. Stored data is encrypted, and inputs and results are reached only through short-lived signed links.
Who handles your data
Each provider works under a contract and only for the purpose shown. The privacy notice has the details.
Amazon Web Services
Hosting, storage, and the GPUs for private jobs
ATON Constellation members
Running shards you mark shareable, never private ones
Stripe
Card payments and, once open, cash payouts to members
Didit
Business checks for customers and identity checks for members
Cloudflare
Protecting this website and the API