Skip to main content
Everabyte serves companies through two commercial paths, and the developer API behaves differently depending on which one you are on. This page explains the difference so you do not build against the wrong assumptions.

​
Direct company accounts

A direct company account is created through the normal signup and checkout flow.
  • You start a trial or buy a paid plan.
  • You create buckets in the dashboard.
  • You create API keys scoped to those buckets.
  • Everabyte bills you directly.
This is the path assumed by most of this documentation. See Quickstart.

​
Partner-managed accounts

Partner-managed customers are provisioned through the partner, not through self-serve signup.
  • There is no self-service partner signup, partner onboarding, or partner pricing page. Partner arrangements are established contractually and provisioned by Everabyte.
  • A customer of a partner does not purchase Everabyte add-ons directly. That restriction is enforced server-side, not just in the UI.
  • Billing flows through the partner. Everabyte does not charge the end customer directly for partner-managed subscriptions.
Do not attempt to create a partner account, change a partner identifier, or route a purchase around the partner relationship through the API. Ownership of partner linkage is backend-controlled and not writable from a client.

​
What stays the same

Regardless of commercial path, the storage API contract is the same:
  • Company-scoped API keys with X-Public-Key and X-Secret-Key.
  • The same scope model and bucket restrictions.
  • The same file, folder, and bucket endpoints.
  • The same encryption pipeline and error envelopes.
What changes is who you contact for billing, contracts, and account-level changes.

​
What the public API does not cover

The developer API is a storage API. It deliberately excludes:
  • partner creation and provisioning,
  • instance and tenant administration,
  • company and user administration,
  • billing and subscription changes,
  • sharing and permission management,
  • audit exports.
Those are dashboard or contractual operations. They are not published here because exposing them as a machine contract would be unsafe and because they are not part of the integration surface.

​
Choosing a path

Onboarding

What to prepare for an enterprise conversation.

Partner integration

Building against a partner-managed account.

Compliance

Technical properties and limits.

Support

How to reach the right team.