sync.cheap

How it works

Mon, 01 Jan 0001 00:00:00 +0000

Workflows as code

A sync.cheap workflow is ordinary Python control flow running inside a constrained VM. Local variables, conditions, and loops execute inside the VM. Anything that reaches the outside world—reading a spreadsheet row, sending an email, waiting for a provider event—is an explicit typed host call.

That split gives agents a flexible language without giving workflow code direct access to credentials or the network.

if trigger["data"]["amount"] > 500:
 await send_slack(
 f"Large order: ${trigger['data']['amount']}",
 connection="finance",
 )

Triggers

Workflows begin in one of two ways:

Pricing

Mon, 01 Jan 0001 00:00:00 +0000

The short version

$10per 100,000 external action calls

New accounts start with $10 in free credit. That is enough for 100,000 action calls at the planned launch price.

What counts

An action call crosses the workflow VM boundary. Examples include:

Counts as a call	Does not count as a call
Send a Slack message	`if` statements and loops
Read a Google Sheets row	Local variables
Ask an LLM for a completion	JSON transformation
Persist workflow state	Comparing values
Wait durably	Receiving the trigger itself

The unit is deliberately close to the infrastructure cost. A scheduled poll that checks one source every 15 minutes uses about 2,880 calls in a 30-day month—or roughly $0.29 at the planned price—before any calls used to act on new work.

Set up sync.cheap

Mon, 01 Jan 0001 00:00:00 +0000

Current status

sync.cheap is not open for self-serve setup yet. The workflow engine, connector catalog, CLI, and MCP surface are being built in public.

When the preview opens, this page will be the handoff point for your agent. You will be able to start with a request like:

Set up sync.cheap from https://sync.cheap/setup, then whenever a
new Google Form response arrives, post a summary to our Slack channel.

What your agent will do

Install or connect the sync.cheap CLI or MCP tools.
Open a login flow and wait while you authenticate.
Determine which connectors and permissions the workflow needs.
Pause for you to connect each account.
Author the workflow, validate it, and simulate a representative event.
Show you the exact draft and ask before publishing it.

The goal is to complete that loop in one agent invocation, including the human authentication steps.