---
title: ScaiDrive
path: overview
status: published
---

ScaiDrive is an enterprise file sync and share platform. A central server keeps the authoritative copy of every file; desktop, mobile, web, and CLI clients keep local copies in step. Teams collaborate in shared folders with NTFS-style permissions, send files to people outside the organization through password-protected links, and find content with both keyword and semantic search.

This documentation covers ScaiDrive from three perspectives — pick whichever one matches what you're trying to do.

## I want to *use* ScaiDrive

You're an end user. You'll sign in through your organization's SSO, browse your shares, upload and download files, share with colleagues, and create external links.

Start with the [user guide](/docs/scaidrive/user-guide). The most common paths:

- [Using ScaiDrive in your browser](/docs/scaidrive/user-guide/web-client) — the web client.
- [Desktop sync app](/docs/scaidrive/user-guide/desktop-app) — keep a local folder in step with the server.
- [Mobile apps](/docs/scaidrive/user-guide/mobile-apps) — iOS and Android.
- [Sharing with your team](/docs/scaidrive/user-guide/sharing-with-your-team) and [external sharing](/docs/scaidrive/user-guide/external-sharing).

## I'm *running* ScaiDrive

You're a systems administrator. You'll provision tenants, manage users and groups, configure SSO, set quotas, enforce compliance policies, and integrate ScaiDrive with the rest of your infrastructure.

Start with the [administration guide](/docs/scaidrive/administration/admin-ui-tour). The day-zero path:

1. [Identity providers](/docs/scaidrive/administration/identity-providers) — connect ScaiDrive to your SSO so users can sign in.
2. [Users and groups](/docs/scaidrive/administration/users-and-groups) — provisioning, lifecycle, SCIM.
3. [Shares and quotas](/docs/scaidrive/administration/shares-and-quotas) — storage allocation.
4. [Compliance policies](/docs/scaidrive/administration/compliance-policies) — retention, DLP, legal holds.
5. [SIEM integration](/docs/scaidrive/administration/siem-integration) — stream audit events to your security platform.

For deployment and ongoing ops:

- [Deployment](/docs/scaidrive/operations/deployment) — install, scale, configure.
- [Health and monitoring](/docs/scaidrive/operations/health-and-monitoring).
- [Troubleshooting](/docs/scaidrive/operations/troubleshooting).

## I'm *integrating* with ScaiDrive

You're a developer building something on top of ScaiDrive — a custom client, a sync target, an AI agent, an analytics pipeline.

Start with [What is ScaiDrive](/docs/scaidrive/introduction/what-is-scaidrive), then:

- [Quickstart](/docs/scaidrive/getting-started/quickstart) — upload your first file in five minutes.
- [Authentication](/docs/scaidrive/getting-started/authentication) — get a token from ScaiKey.
- [API guides](/docs/scaidrive/api-guides) — task-oriented walkthroughs of files, sharing, sync, search.
- [API reference](/docs/scaidrive/reference) — every endpoint, every parameter, every error code.
- [Core concepts](/docs/scaidrive/core-concepts) — the mental model behind the API.
- [Advanced topics](/docs/scaidrive/advanced) — WebSocket events, MCP server, resumable uploads, rate limiting, enterprise compliance APIs.

The [error codes reference](/docs/scaidrive/reference/error-codes) is the right answer when something has gone wrong and you need to know what your code should do about it.

## Conventions

- **Base URL.** Examples use `https://scaidrive.scailabs.ai`. Replace with your own instance URL when self-hosting.
- **API path prefix.** All endpoints live under `/api/v1/`. Paths in this documentation include the prefix.
- **Authentication.** Every request (except `/health` and public share-link endpoints) requires a Bearer token issued by ScaiKey. See [Authentication](/docs/scaidrive/getting-started/authentication).
- **Identifier prefixes.** Resources have typed string IDs: `usr_` users, `grp_` groups, `shr_` shares, `fil_` files, `fld_` folders, `tnt_` tenants, `prt_` partners. Treat them as opaque strings.
- **Sizes and timestamps.** Sizes are bytes (integers). Timestamps are ISO 8601 UTC (`2026-04-23T10:15:00Z`).
- **Response shape.** Successful responses return the resource directly — no `{"status":"ok","data":...}` envelope. Error responses are `{"detail": "<message>"}`. Branch on HTTP status, not on parsing the message.