Managed.
Free for developers through sponsor-supported inference paid for by Picasso.
Pricing
Free for developers.
Picasso does not require a Picasso subscription for individual developers. Use the sponsor-supported managed path, pass through a supported subscription, bring your own keys, or run local models.
picasso / pricingindexed
Pricing
Free for developers
Picasso does not require a Picasso subscription for individual developers. Use the sponsor-supported managed path, pass through a supported subscription, bring your own keys, or run local models.
ManagedFree for developers through sponsor-supported inference paid for by Picasso.
Subscription passthroughUse an existing Claude or ChatGPT subscription where provider terms and account configuration allow it.
BYO API keyBring provider keys and keep billing with the provider.
Four ways to use Picasso.
Pick the credential mode that fits your work. You can switch paths as your needs change.
model accessfour paths
ManagedPicasso payssponsor-supported
Subscriptionprovider planwhere allowed
BYO keyyour accountprovider billing
Localyour hardwareOllama or vLLM
Subscription passthrough.
Use an existing Claude or ChatGPT subscription where provider terms and account configuration allow it.
BYO API key.
Bring provider keys and keep billing with the provider.
Local.
Run against Ollama or vLLM on your own hardware.
The managed path.
Managed mode is the simplest way to start. Picasso handles inference costs through sponsor support, so individual developers can use a serious coding agent without buying a Picasso subscription.
No Picasso subscription required.
Start without a paid Picasso plan.
No surprise Picasso usage bill.
Managed usage is sponsor-supported.
Visible budget state.
See where you stand before a boundary is reached.
Alias based.
Managed mode uses Picasso-operated provider aliases, not user BYO keys or subscription tokens.
Bring what you already have.
If you already pay for a provider plan or manage provider billing, Picasso can work with that path where supported.
model accessfour paths
Managedno setupsponsor-supported
Claude / ChatGPTsubscriptionpassthrough
Provider keysBYOdirect billing
LocalOllama / vLLMyour machine
Provider choice.
Anthropic, OpenAI, Microsoft Foundry, Google, xAI, Qwen, Xiaomi MiMo, Kimi, DeepSeek, Zhipu GLM, MiniMax, OpenRouter, Ollama, and vLLM.
Subscription scope.
Subscription passthrough is scoped to supported Anthropic and OpenAI accounts.
Account control.
Keep provider costs where you expect them.
Local control.
Use models on your own machine or infrastructure.
Usage has a paper trail.
Managed usage records budget state, provider mode, reconciliation status, sponsor attribution, refunds, credits, and redacted export receipts. The free path is still an accounted path.
Budget state.
Session, goal, sponsor, provider, and alias boundaries can stop or ask before spend crosses policy.
Reconciliation.
Provider usage, invoice rows, delayed usage, refunds, and credits can be checked against the ledger.
Redacted exports.
Operational exports are redacted by default and tied back to audit receipts.
No paid tier just to remove sponsors.
Picasso's free path is not made worse to sell an upgrade. The sponsor model is designed around clear surfaces and strict boundaries.
trust boundaryoutside the agent loop
generated codeclean
model outputclean
tool resultsclean
plan documentsclean
routingnot influenced
memoryretrieval only
No sponsor text in code.
Generated files stay clean.
No sponsor text in model output.
Agent responses stay clean.
No sponsor text in tool results.
Execution output remains factual.
No sponsor text in plans.
Plan documents remain work artifacts.
Built for visibility.
Pricing is not only about cost. It is about knowing what the system is doing: budget state, credential mode, permission mode, model state, session history, and sponsor boundaries.
Studiomemory / plans / goals / replay
memorysketchescanvasesgoals
memoryauth module uses argon2id
plan3 files, 2 risks, 4 checks
goal62 percent complete
replay48 strokes recorded
Pricing FAQ.
Is Picasso really free for developers.
Yes. Individual developers can use the managed path without buying a Picasso subscription. Managed usage is funded by sponsor support.
Will I get a surprise Picasso usage bill.
No. Managed mode is designed to avoid surprise Picasso usage bills. Budget state is visible, and boundaries are explicit.
Can I still use my own provider keys.
Yes. BYO API key mode lets you keep inference billing in your provider account.
Can I use local models.
Yes. Picasso can run against local models through Ollama or vLLM.
Do sponsors appear in code.
No. Sponsor content never appears in generated code, model output, tool results, or plan documents.