One connected map of SAP development
The atlas joins what SAP ships and what the community built around it, the writing that explains both, and the people who made them. Every claim is dated and sourced. Nothing is ranked by popularity, and there is no verdict.
Last changed
Why it exists
Building is no longer the hard part; finding what already exists is. The answer to a need is spread over npm, GitHub, SAP's documentation and community posts, and none of them says whether a package is still maintained or whether a tutorial predates the change that broke it. A coding agent gets one look and commits. The atlas puts it in one place, for both.
What is in it
Each ecosystem is a door with its own map: CAP, UI5, ABAP, BTP/BAIP, SAP Commerce, SAP SuccessFactors and SAP Digital Manufacturing. A capability is one concern, such as caching, and its use cases are the outcomes under it; both collect SAP's answer and the community's. Articles explain one area in dated editions, and the graph shows what is joined to what.
Check, contribute, build
Check what is there first, contribute to what is close, and build only what is missing. Each door has a guide for it: CAP, UI5, ABAP and BTP/BAIP. What you build can be added with Add your work.
Readings and prose, kept apart
Readings are crawled: activity, releases, compatibility, each from one number shown beside it. Prose is written and dated: what a thing solves, when not to use it, what it leaves to you. The two never combine into a score.
Drafted with AI
Most of the prose is drafted with AI from the pages it describes, and published by the operator named in the imprint. A page with such text says Drafted with AI once, at its foot, and the JSON carries drafted_with_ai. The label stays after review.
For your agent
Explore and Play
The Playground is the same atlas as a space to fly through, with an orb and a ship of your own, other readers live and small games. For SAP TechEd 2026 it has weekly boards; the leaders stay in the Orb Hall of Fame.
What the atlas refuses to do
- Rank by popularity. Downloads and stars are shown, never used to order.
- Let origin colour a reading. SAP's own and the community's are read by the same thresholds.
- Run anybody's code. Nothing is marked verified; a maintainer's CI result is their dated claim.
- Grade. No badges, no score, no verdict.
- Claim without a source. Every statement links to where it was read, and when.
An independent project
A community project, not affiliated with, endorsed by or operated by SAP SE. The data is public at /graph.json, feedback is public on GitHub, and the lists it draws on are credited on neighbours. Questions are in the FAQ; anything else goes through contact.