# Pricing — Vibestrate

Vibestrate is free and open source. There is no paid tier and nothing to
buy - you pay only for the third-party AI models you choose to run.

## License

- Price: **$0**
- License: **Apache 2.0** for the software (see https://opensource.org/licenses/Apache-2.0)
- Includes: everything - CLI, TUI, Mission Control web UI, the orchestrator, flows, all providers
- Limits: none

## What it does

Vibestrate gives AI coding a CTO-style supervision layer. You describe the
work, choose or pull a reusable flow, fill each phase with the model you want,
and approve the risky gates yourself. If one model becomes unavailable,
unreliable, or overpriced, you can swap the crew without changing the flow.

## What you pay for

You pay only for the *third-party models* you choose to run. Vibestrate
itself never charges and never proxies tokens through a hosted service
— you use your own API keys against each vendor directly:

| Provider          | Pricing                                        | Where to look                |
| ----------------- | ---------------------------------------------- | ---------------------------- |
| Anthropic Claude  | per-token, vendor-set                          | https://anthropic.com/pricing |
| OpenAI Codex      | per-token, vendor-set                          | https://openai.com/pricing    |
| Google Gemini     | per-token, vendor-set                          | https://ai.google.dev/pricing |
| Ollama / llama.cpp | free (runs locally on your machine)            | https://ollama.com            |
| Any CLI provider  | whatever that vendor charges                    | depends                       |

Vibestrate's session ledger surfaces the per-run cost across all of these
so you always know what you spent. You are solely responsible for the
charges your runs incur against these vendors.

## Model independence

Vibestrate is not tied to one model vendor. A flow can run Claude Code for
planning, Codex for implementation, Gemini for review, Ollama for private or
cheap local work, or any CLI provider you add. The point is to keep the process
stable while the crew stays flexible.

## Shared flows

Flows are reusable YAML recipes for software work: planning, building, review,
verification, approval gates, and validators. You can use built-in flows, pull
shared flows from the hub, fork them, or publish your own.

## Telemetry

The Vibestrate software collects none. The Vibestrate process, CLI, and Mission
Control UI do not phone home, do not collect usage data, and do not
require an account. The CLI runs offline; the UI is a local web app
served from the local process on your machine.

The marketing site (`vibestrate.com`) uses cookieless aggregate
page-view analytics via Cloudflare Web Analytics. No individual user
tracking. See https://vibestrate.com/privacy.

## Support

This is a volunteer project. Support is best-effort via GitHub only:

- Issues: https://github.com/guyshonshon/vibestrate/issues
- Discussions: https://github.com/guyshonshon/vibestrate/discussions
- Docs: https://vibestrate.com

There is no email, no Slack, no Discord, no support portal, no SLA.

## Maker

Built and maintained by [Guy Shonshon](https://shonshon.com) under
"Shonshon - Evolving Technologies".

Last updated: 2026-06-18.