Pricing

Questions

Which of Personal and Team am I?

Personal is for a developer paying with their own money, for their own work. If a company is paying, if you are expensing it, or if you are using toryo on work your employer owns, that is Team. The difference is who is paying and what the work is for, not how much of it you do.

How is that enforced?

It is not, technically. Personal and Team run the same app. We would rather trust you than build a surveillance mechanism into a tool that reads your codebase. It is a term of the license, and we ask you to hold to it.

What does Team add?

Team adds a shared brain for your projects, seats managed together, and one invoice. With hosting enabled, your agents can use the project knowledge your teammates' agents have saved. Hosting is included.

Where does a team's knowledge live?

Team project knowledge starts on members' machines. When the owner enables hosting, toryo moves it to our shared service. Personal knowledge stays local. Hosting is included with Team; Enterprise also supports self-hosting.

Does the price include model usage?

No, and deliberately. We sell orchestration and you buy your own tokens: toryo drives your agent under your account, so model usage is billed to you by whoever provides it, at their published rates, and is never marked up by us. It also means our price does not move with your usage. A seat costs the same whether you run four jobs a week or four hundred.

Am I locked into one coding agent?

No. Claude Code, Codex, GitHub Copilot and Cursor all drive work today, you choose which of them a machine offers at all, and a single sequence can use more than one: plan on the harness that plans best, implement on the one you trust with the diff. They are not equivalent, and toryo checks what each can do rather than assuming. The price does not change when you switch, because you were never paying us for the model.

Does it have to phone home?

Not to keep working. A license assertion is signed for a year and carries a further 30 days of offline grace, and a failed check-in never gates the app. Boot still checks in when it can, so a revoked seat stops being valid, but connectivity is not the enforcement surface. The one clock that genuinely stops the app is the trial, and it is signed into the assertion, so it ends on the date promised whether or not the machine ever reaches us again.

What is a seat?

A person, not a machine. One seat covers every machine you work on: activate your laptop and your desktop with the same email and key, and toryo records each machine against your seat rather than replacing the last one.

Can my whole team trial it?

Yes. A trial is per person and self-serve, so everyone who wants to look runs `toryo license trial` with their own email and gets the whole product for 14 days. There is nothing to provision and nobody to ask, and you do not have to decide between Personal and Team before anyone has touched it.

What happens when the trial ends?

toryo stops and asks for a license key. Nothing you built is touched. Activating performs no migration and moves no data, so your memory, library, and code index are exactly where you left them.

Can I start on Personal and move to Team later?

Yes. Team projects sit alongside your personal projects. Your personal projects and their knowledge stay on your machine unless you share them with the team.

Which platforms are supported?

macOS, Apple Silicon or Intel, is the one we stand behind: signed, notarized, run daily. Linux gets the same app as a deb, rpm or AppImage. Windows has the same app, with toryo running inside WSL2; its installer is not signed yet. Linux is tested in containers: real Linux hardware and a user systemd session are unverified.