For GIS teams
You built the platform. This is how the rest of the company finally uses it.
Curated signs in as your people, reads only what they are already allowed to read, and changes nothing in your portal without approval. The requests that never needed you stop arriving. The ones that do still come.
- Built on the ArcGIS Maps SDK
- Your permissions, not a service account
- It writes only what you approve
00 / The premise
AI can process at any scale. Geography is what gives the answer meaning.
A model with no geography answers anyway, fluently and fast, about a place it has never seen. Curated puts the map in front of the AI, on the ArcGIS platform your organization already runs, so the answer arrives with the method and the sources still attached to it.
Esri makes the same case in “AI Needs Geography—and You”, ArcNews, Summer 2026.
01 / The queue
You did not train for this to become a ticket queue.
Somewhere between the degree and the job, the work became other people's requests, and the interesting half of it stopped fitting into the week.
The request that never needed you
A buffer, a join, a count inside a boundary. You have done it four hundred times. It is not why you learned this, and it is most of your week.
The answer that arrived too late
Two weeks in the queue, and by the time the map is ready the deal is signed, the site is gone, or the meeting moved on without it.
The work nobody saw
The layer you built, cleaned and maintained for a decade is carrying a real decision, and the person making it has no idea it exists.
02 / What you do not give up
The portal stays yours. That is not a feature, it is the premise.
Every tool that has ever asked you for a service account asked you to carry a risk on its behalf. This one does not ask.
It signs in as them. Never as us.
Your people connect their own ArcGIS account. Curated sees the web maps they can already see and reads the layers they are already allowed to read. It does not get a service account on your portal.
It writes only what you approve
When it adds or edits records in one of your layers, it shows the change and waits for approval by default. It never deletes a field or a layer, and on layers that keep a change history, every edit can be restored.
You decide what data it can reach
Entitlements are set per organization. A source your team is not licensed for is not there to be reached, whatever anyone types into the box.
Nothing gets flattened
Layers stay layers. The table opens, the related records follow, the attachments download. It is your data, in your shape, with an AI sitting next to it.
03 / Where the line sits
It takes the queue. You keep everything that made you valuable.
The split is clean, and it is the right way round. The work that never needed a specialist stops reaching you. The work that only a specialist can do is finally what you spend your week on.
It takes the queue
The count, the buffer, the trade-area profile, the same demographic pull with a different address. The requests that were never a good use of you, answered the moment somebody asks.
You keep the judgement
Which layer to trust. Which projection quietly ruins the answer. Whether the analysis measures what everyone assumes it measures. That has always been the valuable part, and it stays with you.
You keep the authority
You build the layers. You govern who sees what. You decide which sources the organization is entitled to reach. Curated runs inside those decisions, and it does not get a vote on them.
Your value was never the buffer. It was knowing which layer to trust, and which question the person should have asked instead.
None of that is in the queue we are taking off you. All of it is in the playbooks you are about to write.
04 / Your method, running without you in the room
The way you do it is the thing worth scaling.
You already know how a site should be judged here. Which layers, which thresholds, which factor quietly matters more than the others, and what disqualifies a site no matter how well it scores. Today that lives in your head, and it walks out of the building when you do.
A playbook is that method, written down and running. It turns the one thing you could never delegate into the one thing the whole organization can use, with your name on it.
How a playbook worksYou set the weights
You set the thresholds
You name the disqualifiers
You choose the layers it trusts
05 / Shipping next
Where the workspace goes deeper into your workflow.
Built with the GIS teams already using it, and shipping on a roadmap you can see.
In development
Scenes and 3D
The workspace is a 2D map today. Scene support is on the way.
Geoprocessing from the conversation
Running your own geoprocessing tools by asking for them, on the layers you already govern.
More ways to bring data in
CSV and Excel files import into a layer today. Shapefiles, GeoJSON and file geodatabases are next.
The questions your team will ask before anyone else does.
-
Is this going to replace our GIS team?
No. It takes the routine request off your queue and leaves the work that actually needs you. Curated does not build layers, does not decide whether your data is fit for a question, and does not govern who sees what. Those stay with your team, and they were always the valuable part. What changes is the ratio: far less of your week on the fortieth buffer, far more of it on the work only you can do.
-
Do we have to give you a service account?
No. Each person connects their own ArcGIS account, Online or Enterprise, and Curated operates as that user. Your groups and your item-level permissions apply, unchanged. The permission model you spent years building is the permission model it obeys, which means you never hand a vendor keys to the portal.
-
Can it break something in our portal?
It works as the signed-in user, so it can only change what that person is already allowed to edit. Writes to a layer wait for approval by default and it never deletes a field or a layer. Layers Curated creates keep a change history, and a layer's owner can turn it on for any other, so edits there can be restored. Styling, filters and other map changes happen in the view and can be undone.
-
How do we check its work?
This is exactly why the method is visible. Every playbook names the factors it weighs, the thresholds it applies and the disqualifiers it enforces, and Curated says which one it intends to run before it runs it. Every number carries the source it came from and the date it was published. So an answer can be traced, checked and challenged by the person who knows the data best, which is you.
-
Our data is the good part. Does it stay ours?
Your data is not training data. Not now, and not on a future roadmap. It answers your organization's questions and does nothing else.
Point it at a web map you already trust. Ask it something you already know.
The fastest way to judge this is to aim it at a map your own team built, ask a question you can already answer, and see whether it does what you would have done.
Twenty minutes, on your own portal, with your own permissions.