A place for your team
Planned organization and project membership connects identity with access, so a shared workspace has clear boundaries.
Alchemist Cloud
The planned hosted home for your team's projects, media, and review. Built on the same service architecture as Alchemist Server, with the infrastructure operated for you.
Planned · Hosted serviceOne identity. One project. One media library.
01 — The shared room
The hosted-services plan starts with the essentials: who can join, what they can see, and how the right version reaches them.
Planned organization and project membership connects identity with access, so a shared workspace has clear boundaries.
Review links are planned as scoped, expiring, revocable access to a project, version, or asset.
The browser review phase will stream registered proxy artifacts, using the playback and caching foundations already in Alchemist Web.
Timecoded comments are part of the first review milestone. Reviewers can discuss the work against the version they were sent.
The Pro roadmap adds verified, resumable publishing and a Server media provider so shared assets can be reached from the native workflow.
Connected editing follows review. Its planned local history and server reconciliation will let project changes travel between sessions.
02 — Familiar tools, connected
The plan extends the existing Alchemist applications. The browser player, timeline, and media cache remain the foundation as shared services arrive.

The first connected phase adds share-link access, an asset and version list, proxy playback, and timecoded comments.
The native client plan brings sign-in, browsing, publishing, and eventually project synchronization into the desktop app.
A later phase connects project history to the service, with local caching and explicit offline and reconnect behavior.
03 — The hosted roadmap
Cloud depends on a proven shared service, reliable media identity, and project history. The roadmap sequences those foundations before the hosted rollout.
Alchemist already has browser playback and editing, native media providers, and local project workflows to build on.
Team identity, project access, verified media storage, and signed delivery links establish the Server foundation.
Prove shared access and media playback through review first. Add project history synchronization and reconnect behavior afterward.
Operate the same service architecture with managed storage and databases, organization quotas, and an operational runbook.
04 — Choose who operates it
Server is the self-hosted direction; Cloud is the hosted direction. Both are planned around the same clients and service architecture.
| Responsibility | Alchemist Cloud · planned | Alchemist Server · planned |
|---|---|---|
| Infrastructure | Operated by Alchemist | Operated by your team |
| Media and data | Managed databases and object storage | Your deployment and S3-compatible storage |
| Editing and review | Connected Alchemist Web and Pro | Connected Alchemist Web and Pro |
| Team boundaries | Organization and project access | Organization and project access |
| Delivery stage | After the shared service is proven | Self-hosted foundation first |
Across the suite
Explore the applications and workflows the hosted service will connect.
Get updates as Alchemist Cloud moves from the service foundation to hosted review and editing.
Cloud is planned. No hosted subscription is available yet.