About
A project developer, starting in Peru.
Orateva was created to develop forest carbon projects directly, alongside the communities who hold the land.
Origin
Why the company exists
Forest carbon has no shortage of intermediaries. What it lacks is people who stay on the ground long enough for a project to hold together.
Orateva was built to develop projects itself: to sit in the first conversations, to walk the slopes, to write the agreements, to run the nurseries and to carry the monitoring through the years that follow. The work only makes sense if someone is accountable for it from beginning to end.
That choice shapes everything else. It sets the pace of the company, the size of its first commitment, and the order in which things are announced.
How we work
Three commitments
-
01
The territory comes first
A project is designed from what the land can carry and from the practices already in place, not from a carbon target chosen in advance.
-
02
Communities decide with us
Roles, commitments and benefit sharing are defined together and written down. Nothing about a community is published without its agreement.
-
03
We name the stage we are at
Design, validation, registration and verification are distinct steps. We say which one a project has actually reached, and we date what we publish.
Where we are
One territory at a time
Orateva is starting with a single project, in the high Andean territories of Áncash, in northern Peru.
Peru was not chosen for its carbon market. It was chosen because the puna is one of the ecosystems where restoration changes the most: water retention, soil stability, native forest cover and grazing land all move together.
Other projects in Peru, in Latin America or elsewhere will follow once this one is consolidated and the local, technical and financial conditions allow it.
Team
The people behind the work
Orateva is run by a small team working between Europe and Peru, with local expertise on the ground in Áncash.
Project development, community relations, forestry and monitoring are held by people who have carried these responsibilities on other projects before. Public presentation of the team follows the same rule as the rest of the site: it is published once it is stable.