Pilot guide
Pilot Availsync in 10 minutes.
This is the self-serve path for first users: verify the product, run in observe mode, then turn on enforcement once the dashboard proves value.
Start free
Create a workspace and agent. The free plan includes 3 agents, 2 protected resources, and 3 active work claims.
Run verification
Use the dashboard verification flow to see Availsync resolve a real conflict between two agents without touching your repo.
Switch the pilot agent to Observe
Observe mode lets the automation run normally while Availsync records what it would have blocked.
Install the Node SDK
Add @availsync/node to the automation project and wrap the repo work with withClaim.
Run one guarded repo task
Use resource repo:owner/repo as the safe default. Blocked enforce-mode runs should exit with skip_run.
Confirm value
Check Activity for real runtime calls and Overview for blocked or would-have-blocked work runs.
Success criteria
What a good pilot looks like
Scope for the first pilot
Use repo-level resources for the first pilot. Availsync blocks simultaneous work on the same resource, but it does not yet infer dependencies between separate project keys or sync external calendar providers.