Where FlexVault is headed

This is the running log of what we're building, in the order we expect to touch it. Nothing here is a promise or a date. We treat it like a diff against reality, rebased every quarter as the alpha teaches us things.

Cadence reviewed quarterly Source alpha feedback + engineering priorities Status FlexVault is in open alpha
Looking for what's already shipped? Release Notes· Discord announcements
~ In progress + New ? Idea

Building

actively being developed

With branching now a native part of the core, the largest piece in flight is what that unlocks: interactive conflict resolution, plus closing rough edges across the engine, IDE, and migration integrations.

~

Engine plugin hardeningunityunrealgodot

Closing the rough edges in the native engine editor integrations, including more actions handled over the background daemon instead of spawning the CLI for every click.

~

VS Code hardeningide integrations

The same background-daemon work as the engine plugins above, applied to the VS Code extension.

~

Interactive resolvecore

Right now conflict resolution is only "take theirs" or "take mine." Interactive resolve, allowing piecemeal resolution of conflicts, is being implemented on top of the multi-writer detection that branching now makes possible.

+

Informational file lockingcore

See who already has a file open before you touch it. Advisory rather than enforced, so it stays out of your way when nobody's actually conflicting.

~

Bridge: run alongside your current SCMenterprisemigration

A gradual migration path so a studio can trial FlexVault against a live Perforce or Git history before committing to a cutover, with clearer status and conflict reporting as it runs.

~

A background agent for automatic snapshots and publishingagent

A lightweight agent that starts with your machine and takes over the routine work: automatic snapshotting as you go, configurable publishing, and conflict resolution, so the CLI and editor plugins stay in sync without anything needing to be launched by hand.

~

Docs & community that scale past early adoptersdocs

Getting-started paths and a Discord that hold up once the audience is bigger than the people who already know the team.

Planned

decided, not yet started

Scoped and on the list, but work hasn't started yet.

?

A native desktop appdesktop

A standalone window onto workspace and sync status for people who'd rather not live in a terminal.

?

On-prem Enterprise deploymententerprise

Self-hosted FlexVault for studios that need to keep everything behind their own walls.

?

Cloud authenticationenterprisecore

Managed sign-in for cloud-hosted workspaces, so getting everyone connected doesn't mean handing out shared credentials.

Exploring

early and unscoped

Directionally likely, but not yet scoped or prioritized against the rest of this list.

?

JetBrains pluginide integrations

Native integration for Rider and the rest of the JetBrains line, in the same vein as the Unity, Unreal, Godot, and VS Code plugins.

?

Visual Studio integrationide integrations

Still early. Scope and priority against the rest of the IDE list aren't settled yet.

This page reflects our current thinking, not a contract. Items get renamed, merged, reordered, or dropped as the alpha teaches us more about what studios actually need. If something here matters to you, or something's missing, tell us.

→ Send feedback on this roadmap