Grounded environmental answers, faster
Work faster for the environment. It's urgent.
Environmental data work still takes too long: databases are fragmented, tools are opaque, and results are hard to trace. Volca helps teams get faster answers from real LCA data while keeping the path to each answer inspectable — in the browser, on desktop, or through an engine you can run yourself.
Built for environmental work that has to be trusted
Less time lost in fragmented tools
LCA work should not require a maze of exports, disconnected databases, and manual checks before you can even understand what you are looking at.
Answers with a visible path
Volca keeps the route to an answer inspectable: activities, direct exchanges, trees, inventories, mappings, impact methods, and source records stay close to the result.
One engine, several ways to work
Start in the hosted product, explore locally with the desktop app, or run and integrate the open-source engine through API, Python, CLI, or MCP workflows.
Which one are you?
I'm an analyst or practitioner
You work with LCA databases, methods, and environmental assessments. You need faster inspection, clearer results, and a tool that keeps the path to the answer visible.
Start here: try the hosted product or desktop app, see if Volca fits your workflow, and upgrade only when it becomes part of your routine work.
See the analyst path →
I'm a technical team or developer
You want to run Volca on your own infrastructure, integrate it with the Python client, API, or MCP, or use it as the engine behind a custom tool, agent, or internal platform.
Start here: download the binary from releases, load a database, and call it from Python, the API, or the REPL in minutes.
See the get-started page →
I'm building something
You have a specific workflow, dataset, or deployment need. You want a scoped conversation rather than a generic self-serve path.
Start here: describe your workflow and constraints, and we can figure out together what makes sense.
Talk to us →
I want to explore locally first
You prefer a local desktop path before committing to anything hosted. Start with the desktop app and see how Volca behaves on your own machine.
Start here: sign up and access the desktop app from your account.
See the desktop path →
See the idea on real data
Open an activity and follow the data
Use an Agribalyse example to move from search to activity details, direct exchanges, trees, inventories, and impact results.
Inspect an example →
Ask a question without losing the sources
Connect an assistant to Volca so a plain-language answer can still point back to datasets, methods, activities, and evidence.
See grounded answers →
Check what works today
Review current examples, performance notes, and boundaries before treating Volca as part of a serious workflow.
See examples and benchmarks →
Start where it makes most sense
Try the hosted product for the fastest start. Use the desktop if you prefer local exploration. Deploy the open-source engine if you want full control.