> ## Documentation Index
> Fetch the complete documentation index at: https://docs.everabyte.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise onboarding

> What to prepare before an enterprise conversation, and how a company moves from trial to a contracted deployment.

This page describes the information and decisions that make an enterprise onboarding conversation productive. It is a preparation guide, not a contract.

## Before you start

Bring answers, not questions, where you can.

### Account and ownership

* Legal entity name and the jurisdiction it is registered in.
* Who will own the company workspace.
* Who will administer users and API keys.
* Whether the workspace should be isolated from any existing Everabyte account.

### Workload shape

| Question | Why it matters |
| - | - |
| How much data now, and after 12 months? | Storage and plan sizing |
| Average and maximum object size | Upload strategy and limits |
| Read/write ratio | Bandwidth and CDN decisions |
| Request rate at peak | Rate limit expectations |
| Number of buckets and environments | Isolation design |
| Retention obligations | Bucket and file retention settings |

### Security and compliance

* Required jurisdictions for stored data.
* Whether CDN delivery is acceptable.
* Whether your auditors require that no Everabyte service may ever process decrypted content. If so, raise it in the first conversation: authorized operations and platform maintenance workflows process decrypted content by design.
* Certification evidence your customers require.
* Whether you need audit data exported programmatically.
* Your own RTO and RPO expectations, and whether you plan an independent second copy.

### Integration

* Language and framework of the consuming service.
* Where secrets will live.
* Whether you need server-side only, or a browser component.
* Whether you are migrating from another storage provider, and how much data is involved.

## The onboarding sequence

The exact sequence depends on the arrangement. In general:

1. **Scoping.** Workload, residency, security, and commercial shape are agreed.
2. **Contracting.** Terms, volume commitment, and support expectations are set.
3. **Provisioning.** The company workspace is created. You do not create it yourself through a partner path.
4. **Access setup.** Owners are invited, then users, then API keys.
5. **Integration.** You build against the same public API described in this documentation.
6. **Migration.** If you are moving data, plan copy, verification, and cutover explicitly.
7. **Handover.** Support contacts and escalation paths are confirmed.

> [!NOTE]
>
> Provisioning details are handled by Everabyte. This documentation does not describe administrative or provisioning endpoints, and you should not need them.

## Migration planning

If you are moving existing data in:

1. Create target buckets in the required locations.
2. Copy or re-upload in batches you can verify.
3. Compare object counts and sizes per batch.
4. Record `fileId` and `versionId` for anything critical.
5. Keep the source until your own verification passes.
6. Cut over reads only after writes have stopped on the source.

Do not decommission the source based on a successful upload response alone. Verify.

## What you should not expect

| Expectation | Reality |
| - | - |
| Self-service partner signup | Not available; partner relationships are contractual |
| Automatic cross-region replication | Not part of the standard service |
| Guaranteed RTO/RPO figures | Not published for standard plans; agree them contractually if needed |
| Zero-knowledge encryption | Not offered; decryption is limited to authorized operations and controlled maintenance workflows |
| Programmatic partner or tenant provisioning | Not published |

## After onboarding

Once the workspace exists, everything else in this documentation applies unchanged:

> **[Quickstart](https://docs.everabyte.com/getting-started/quickstart.md)**
>
> Make your first request.

> **[API keys](https://docs.everabyte.com/authentication/api-keys.md)**
>
> Create scoped keys in the dashboard.

> **[Data residency](https://docs.everabyte.com/security/data-residency.md)**
>
> Plan bucket locations.

> **[Compliance](https://docs.everabyte.com/security/compliance.md)**
>
> Technical properties and limits.

## Contact

Enterprise and partner inquiries: [support@everabyte.com](mailto:support@everabyte.com).

Include the workload shape and the specific requirements above. A precise brief shortens the process considerably.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.