Provider Agreement
This agreement is for people who run umbra host. As a provider you host public, platform-approved models on your own Mac, usingyour own Hugging Face key. You cannot read the prompts or outputs that flow through your machine, and the network is designed so that trust comes from attestation, not from a promise. This agreement applies to you in addition to the Terms of Service andPrivacy Policy.
Experimental alpha. No payouts. Umbra is in an experimental alpha. No payments are processed. There areno charges to developers or API users andno payouts to providers. All billing, payment, top-up, and payout features are disabled and deferred until a future general-availability release. Any base pay, on-demand earnings, or wallet balance you see accrues for transparency only: the amounts are projections, are illustrative and non-binding, and arenot payable during alpha. Nothing on the platform moves real money during alpha.
This is a draft, not legal advice. This document is a good-faith draft prepared for the operator and their counsel to review. It is not legal advice and does not create any attorney-client relationship. Bracketed placeholders (such as the governing-law jurisdiction) are to be completed by counsel before any release.
1. Who this is for
This agreement covers anyone who enrolls a Mac as an Umbra provider and runs the provider client (umbra host). You must be at least 18 years old and able to enter into this agreement. A single Umbra account can act as both a developer (using API keys) and a provider (hosting models).
2. What you host, and with whose key
- You host public, open-weight models that the platform has approved for the catalog. You do not host private, secret, or buyer-supplied weights. Public model files are not treated as secret.
- You download model files using your own Hugging Face credentials. Umbra never receives your Hugging Face key, and the download happens under your account with Hugging Face.
- You are responsible for complying with each model's license, Hugging Face's terms, and the laws that apply to you. You confirm you have the right to download and serve each model you host.
3. Prompt privacy (you cannot read the work)
The core of Umbra is that you, the machine owner, cannot read the prompts or outputs that pass through your provider. The design assumes the machine owner may be adversarial and closes the software paths to the inference process rather than relying on your good behavior:
- Inference runs in-process (no inference server, socket, or IPC to intercept), and prompt and output buffers arezeroized after each request.
- The runtime is hardened against debuggers, memory reads, and binary tampering, and the network is designed to attest that this lockdown is in place (Secure Enclave, SIP, MDM/MDA, and code-identity).
- You agree not to attempt to read, capture, log, reconstruct, or exfiltrate prompts or outputs, and not to circumvent, disable, or tamper with the privacy or attestation mechanisms. Doing so is a material breach.
Accuracy note: full hardware enforcement (real Apple Managed Device Attestation, or MDA) is in progress and not yet enforcedacross the alpha network; a stand-in signer may be used during this period. Attestation is the property we are hardening toward, not something fully enforced end to end today.
4. Attestation and enrollment
Trust on the network is established by attestation, not by a promise. To host at the attested tier, you enroll your Mac (which can include MDM/MDA enrollment) so the operating system itself can report your device's security state. By enrolling you authorize the platform to verify your hardware identity and security posture on an ongoing basis. You agree to keep your machine in the attested configuration while hosting and not to spoof, replay, or falsify attestation signals.
5. Your responsibilities
- Run a genuine, unmodified provider client, and keep your machine, account, and credentials secure.
- Provide accurate device and account information (for example the machine name, chip, and unified-memory size used for routing and attestation).
- Be responsible for your own electricity, bandwidth, hardware wear, network connection, and local taxes or fees that may apply to you.
- Comply with the Terms of Service acceptable-use rules and all laws that apply to you.
6. Earnings during alpha (transparency only)
The console may display base pay (for being attested, online, and ready) and on-demand earnings (per-token) so you can see how the model is intended to work. During the alpha these figures areprojected, illustrative, and non-binding bookkeeping:
- No payouts are made during alpha. Accrued amounts are not a debt, are not redeemable, and are not withdrawable. They have no cash value.
- Displayed rates, tiers, and totals are subject to change and may be reset during the alpha. Nothing here is a promise of future payment.
- If and when payouts are introduced at general availability, they will be governed by a separate, updated agreement that you will be asked to accept, and may require identity verification (KYC) and tax information before any money moves.
7. Acceptable use for providers
You may host approved uncensored or unfiltered models (the platform is a neutral pipe with provider approval), but you may not host models that are clearly illegal, host models you lack the rights to serve, use the provider client to attack or de-anonymize users or the network, or use it to circumvent metering, routing, or access controls. The platform may remove a model from the approved catalog at any time.
8. You can stop anytime
Hosting is voluntary. You may stop hosting and unenroll your machine at any time, for any reason, with no penalty. Because no payouts are made during alpha, stopping forfeits nothing of cash value. We may also suspend or terminate your participation at any time, including for suspected breach of this agreement, the Terms of Service, or applicable law.
9. As-is, no warranty
The provider client and the network are provided "as is" and "as available," without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, availability, accuracy, or non-infringement. The software is early-stage alpha and may change, break, or be discontinued. You run it at your own risk and are responsible for your own hardware.
10. Limitation of liability
To the maximum extent permitted by law, Umbra and its operators will not be liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost data, hardware wear, or energy costs, arising from your operation of a provider machine. Our total liability is limited to the amount actually paid to you, which, during the alpha (when no payouts are made), is zero.
11. Indemnification
You agree to indemnify and hold harmless Umbra and its operators from claims arising out of your operation of a provider machine, the models you choose to host, or your violation of this agreement, the Terms of Service, a model license, or applicable law.
12. Governing law
This agreement is governed by the laws of [governing jurisdiction, to be set], without regard to conflict-of-laws rules. Disputes will be resolved in the courts of that jurisdiction.
13. Changes
We may update this agreement as the network evolves. The "Last updated" date reflects the latest version; continued hosting after a change means you accept the updated agreement.
14. Contact
Questions about hosting? Reach us at[email protected].