LEARN / LOCAL-FIRST
Your machine. Your providers.
Your accumulated intelligence.
EvoForge puts no application server between you and your model provider. What it learns about you stays on disk where you can read it.
What stays on your computer.
- Keys. Provider credentials are stored on your computer and used only for the services you configure.
- Sessions and files. Your conversations, the files the agent works on and the artefacts it makes stay local.
- Memory and skills. What EvoForge learns lives in inspectable assets you can open, edit, version, disable or roll back.
None of these are uploaded.
Straight to the model you chose.
When the agent uses a cloud model or a connected service, the request goes from your computer directly to that provider. All outbound traffic passes through one network layer, so it can be reviewed, routed through your proxy, or cut off in one place. With a local model service, the work does not need to leave your machine at all.
This is also why EvoForge sells feature licences rather than tokens: there is no model usage passing through EvoForge to resell.
Computer control
Browser, any desktop app, a persistent shell and remote servers — all behind permissions you set.
Read03 / FAQFrequently asked questions
Price, keys, privacy, platforms, models, modules, updates — the questions people ask first.
Read04 / ABOUTAbout EvoForge
Who makes it, what it is for, and the principles it is built on.
ReadKeep your work on your machine.
Windows and macOS. Bring your own model key or a local model.