studio
Why does validation fail on the merge step?
Input B is in EPSG:32634, input A is in EPSG:4326. A reproject step before the merge fixes it.
Add Reproject
before merge · 32634 4326
ApplyDiscard
Earth Observation workflows you candesign in a browser, scale without rewrites, or run as a service.
Design visually, run at any scale and deliver products as maps, services and APIs, on a platform built for Earth Observation, end to end.
Now in private beta
One workspace for every Earth Observation project
No handover between tools, no custom scripts holding it all together, no rebuilding when requirements change. Every geospatial workflow stays in one place, from first idea to final delivery.
Build EO workflows visually, without code
Connect the geospatial data you need, add your own AI models or pick from the ones we provide, and lay the workflow out on a canvas. The platform checks it holds together as you build, and every workflow is versioned and ready to reuse on your next project.
Run your workflows at scale and deploy them as services
Your workflows run fast on our processing engine on demand with parallel scheduling, GPU acceleration & automatic memory management. Decide how they execute and scale whenever you need to. The results are published through OGC endpoints and REST API, and can be easily served into the tools your users already work in.
Our AI assistant works alongside you at every step
Not just a chat box in the corner. One AI assistant across Data, Studio, Products and your User Profile, with the context of the page you are on.
The assistant operates on your current workspace state and proposed changes take effect only upon your approval. Accelerate your development and reach every capability of our platform from day one.
Built for the teams who have to deliver
Data engineers & geospatial teams
Every project rebuilds the same stack
Your geospatial data, models and runs sit in one workspace, so what you build for one client becomes what you deliver to the next. The workflow stays versioned, so the next delivery starts from a working system rather than an empty script.
Domain experts & practitioners
Try the idea before anyone writes code
Build the method visually in Studio, with the AI assistant proposing the next step, and run it over a small area to see the result. There is no geospatial engineering to learn first, so the expertise stays with the person who has the question.
Research groups & public bodies
The method has to outlive the project
Prove the method on one area, then scale it to a whole country without rewriting it and publish it through the geospatial standards your users already work in. The service stays live between runs, for the department or the consortium that inherits it.
Managed on our platform
Whichever problem brought you here, the geospatial workflow you prototype is the one you put into production. When it has to run reliably, at scale and reach the people who depend on it, RedEdge handles the execution, scheduling and monitoring, and publishes the results to the services your users already work in, so your team can stay on the analysis rather than the engineering around it.
Learn more about the RedEdge platformEverything you need to run Earth Observation workflows in production
From a working prototype to a service other people depend on, on one geospatial platform
We're onboarding a limited group of early users.