Skip to main content
This page describes capability availability as documented. It is not a live incident feed. For active incidents, contact support@everabyte.com.

​
Surfaces

​
S3-compatible gateway

An S3-compatible gateway exists and supports SigV4, single-PUT, multipart upload, range reads, and bucket/object listings. Several third-party tools can work through it. However, it is gated by a platform flag and is not enabled for every deployment or account.
Do not design an integration that assumes S3 compatibility. Build against the REST API, or confirm gateway availability with support before committing.
See S3 compatibility for what the gateway covers when enabled.

​
Feature states

Not every capability follows the same lifecycle. When reading this documentation, distinguish: If a documented endpoint returns an unexpected 403, check whether the capability is gated rather than assuming a scope problem.

​
Trial restrictions

Trial accounts are subject to enforced restrictions:
  • maximum file size of 100 MB,
  • one active API key,
  • reduced audit retention,
  • MCP refused,
  • compliance features refused,
  • storage add-ons refused.
These are backend-enforced. There is no client-side workaround.

​
Detecting availability from your side

There is no public capability-discovery endpoint. Practical approach:
  1. Attempt the operation with a correctly scoped key.
  2. Treat 403 API_KEY_SURFACE_DENIED as “this route family is not available to keys”.
  3. Treat a gated feature as unavailable until support confirms otherwise.
  4. Cache negative results; do not hammer a disabled surface.

​
Maintenance and changes

API changes are reflected in this reference. There is no public feed for API changes at this time; check the pages you depend on when you upgrade, and contact support if you need advance notice of a specific change.

S3 compatibility

Gateway scope when enabled.

Limits and quotas

Numeric limits by plan and trial.

Support

Escalation path.

Error codes

Stable codes.