The starter period runs 14 days on Ambervane Studio, with $18 of metered credit, connectors for every supported model, and staging runs so you can inspect each result before it reaches production.

Every run reports the tokens, compute seconds, and storage it consumed. Those figures roll into one line on your monthly statement, and your plan credit is drawn down first.

Scheduling, retries, secret rotation, staging environments, and the queue that fans work out to your connectors. You keep ownership of the data; we keep the plumbing upright.

Yes. One command writes every workflow definition, run history, and secret reference to a folder you control, in plain files that run outside Ambervane without edits.

Studio is built around one operator and a single workspace. Guild adds shared review queues, seat-level permissions, audit exports, and a second staging region.

Small studios and operations groups running repeatable work on a deadline — roughly four to sixty people, with at least one person who can read a run log.

Partly. Guild bundles the sending, enrichment, and reporting connectors most teams pay for separately; media spend itself still bills to your own accounts.

Point the workspace at any repository you already host. Ambervane reads the branch you nominate, writes to a side branch, and never force-pushes over your history.

Bring your own key on any tier. Runs charged to your key are excluded from metered usage, and the key stays in the encrypted vault attached to that workspace.