Doc sourceDoc sourcetypeDocumentation collected and cited. Evidence, like a sample.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

SAP/architecture-center

The repository the SAP Architecture Center site is built from: SAP's reference architectures, each drawn as editable draw.io diagrams, with Mermaid for flows.

A reference architecture here is SAP's drawing of how applications, data and AI work together for one problem, at the product and service level, across SAP cloud and on-premises, written as a readme with its solution diagrams in a draw.io folder beside it. The repository is a Docusaurus site under Apache-2.0 that takes feature requests, bug reports and contributions through GitHub, and its guidelines tell a contributor how to structure a page and to draw in the SAP BTP Solution Diagram Guidelines style. Beside the pages, the site runs an Architecture Validator that checks an uploaded diagram for common issues, and it reads draw.io files only.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Architecture diagramsBTPArchitecture diagramscapabilityDrawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.

Who is behind it

SAP Architecture CenterSAP Architecture CenterOrganisationMaintains this
In the atlas: maintains 1, wrote 26
SAPSAPOrganisationMaintains this
In the atlas: maintains 137, wrote 14
@SAP
maintainersChristoph SzymanskiPersonContributes to this
In the atlas: contributes to 2
@1084565
AbhishekPersonContributes to this
In the atlas: contributes to 1
@abhissharma21
Abhijeet KulkarniPersonContributes to this
In the atlas: contributes to 1
@abklgithub
Adarsh HegdePersonContributes to this
In the atlas: contributes to 2
@adarshnarayanhegde
Ajit Kumar PandaPersonContributes to this
In the atlas: contributes to 1, wrote 3
@AjitKP91
aldapoohPersonContributes to this
In the atlas: contributes to 1
@aldapooh
Ali AbuhassanPersonContributes to this
In the atlas: contributes to 1
@AliAltivate
Alper DedeogluPersonContributes to this
In the atlas: contributes to 3, wrote 2
@alperdedeoglu
Uma AnbazhaganPersonContributes to this
In the atlas: contributes to 2
@anbazhagan-uma
Jimmy Henry-DouglasPersonContributes to this
In the atlas: contributes to 1
@AndItDontFade
61 contributors

What it declares

Every artifact

Type
Doc source
Origin
By SAP
Use as
A reference

Tasks this contributes to1Beta

Check a BTP solution diagram against the guidelineA BTP solution diagram exists, and before it goes into a document or a review someone wants to know whether it follows SAP's visual language rather than only looking about right.CoversSAP's own check of a finished diagram
What it does

The Architecture Validator on the SAP Architecture Center site takes an uploaded diagram and reports common issues. It reads draw.io files and nothing else.

Remaining work

Upload the diagram by hand and read the report. The readme names no individual rules, so which breaches are caught has to be found out by using it.

All options on the Architecture diagrams page →

Connections1

SAP/architecture-center connectionsSAP/architecture-centerPROVIDES→ demonstrates1demonstrates authoredArchitecture diagrams

README

quoted from SAP/architecture-center under Apache-2.0, read
SAP/architecture-center/README.mdOn GitHub

REUSE status Deploy main site to Cloudflare Periodic Link Checker CodeQL OpenSSF Scorecard Security Audit Scorecard supply-chain security

SAP Architecture Center

SAP Architecture Center

Reference architectures are templates in their simplest form. They generalize specific implementations of software with a common set of components, vocabulary, or configuration. In the SAP context, this means showing how applications, data, and AI operate at the product and service level, and how you can take advantage of repeatable best practices to optimize your SAP cloud and on-premises investments.

A reference architecture outlines the interactions between various services, showcasing how they work together seamlessly. It also demonstrates how these services integrate with business applications from SAP, partners, and third-party providers. This holistic view helps organizations understand the components needed to build a cohesive and efficient system. These templates provide a standardized approach to designing systems, ensuring best practices and optimal configurations are followed. They can easily be customized or adapted to a customer's unique environment and provide a foundation for adopting the latest cloud innovations from SAP.

Requirements and Setup

Prerequisites
  • Node.js >= 22.0
  • npm or pnpm
  • Git
Local Development Setup
1. Clone the Repository
git clone https://github.com/SAP/architecture-center.git
cd architecture-center
2. Install Dependencies
npm install
3. Start Development Server
npm start

This will start the Docusaurus development server. Open http://localhost:3000 in your browser to view the site.

The development server supports hot reloading - changes to source files will automatically refresh the browser.

4. Build for Production
npm run build

This generates static content in the build directory that can be served by any static hosting service.

5. Run Linting
npm run lint          # Check for linting errors
npm run lint:fix      # Auto-fix linting errors
6. Security Audit
npm run security:audit        # Check production dependencies for vulnerabilities
npm run security:audit-fix    # Automatically fix vulnerabilities where possible
npm run security:check        # Run audit and check for outdated packages
npm run security:update       # Update packages and fix vulnerabilities

Note: The security audit checks only production dependencies (excludes devDependencies) to focus on what gets deployed.

For detailed contribution guidelines, refer to the Community of Practice | Intro.

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Security / Disclosure

If you find any bug that may be a security problem, please follow the instructions in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2026 SAP SE or an SAP affiliate company and architecture-center contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.

Apache-2.0, read

History

Latest

v3.2643.3

  1. v3.2643.2

  2. v3.2643.1

  3. v3.2642.2

  4. v3.2642.1

  5. v3.2641.4

  6. v3.2641.3

  7. v3.2641.2

  8. v3.2641.1

  9. v3.2640.3

  10. v3.2640.2

  11. v3.2638.3

  12. v3.2637.1

  13. v3.2635.3

  14. v3.2635.2

  15. v3.2635.1

  16. v3.2634.3

  17. v3.2634.2

  18. v3.2634.1

  19. v3.2633.1

  20. v3.2632.1

  21. v3.2631.1

  22. v3.2630.2

  23. v3.2630.1

  24. v3.2629.1

  25. v3.2628.1

  26. v3.2627.1

  27. v3.2626.2

  28. v3.2626.1

  29. v3.2625.1

  30. v3.2624.2

  31. v3.2624.1

  32. v3.2623.4

  33. v3.2623.3

  34. v3.2623.2

  35. v3.2623.1

  36. v3.2621.2

  37. v3.2621.1

  38. v3.2620.5

  39. v3.2620.4

  40. v3.2620.3

  41. v3.2620.2

  42. v3.2620.1

  43. v3.2619.3

  44. v3.2619.2

  45. v3.2619.1

  46. v3.2618.2

  47. v3.2618.1

  48. v3.2617.4

  49. v3.2617.3

  50. v3.2617.2

  51. v3.2617.1

  52. v2.2616.1

  53. v2.2615.1

  54. v2.2613.1

  55. v2.2612.3

  56. v2.2612.2

  57. v2.2612.1

  58. v2.2611.2

  59. v2.2611.1

  60. v2.2610.1

  61. v2.2608.1

  62. v2.2606.1

  63. v2.2605.1

  64. v2.2603.1

  65. v2.2551.1

  66. v2.2549.1

  67. v2.2548.1

  68. v2.2547.1

  69. v2.2546.2

  70. v2.2546.1

  71. v2.2545.5

  72. v2.2545.4

  73. v2.2545.3

  74. v2.2545.2

  75. v2.2545.1

  76. v1.2543.1

  77. v1.2542.1

  78. v1.2541.1

  79. v1.2539.1

  80. v1.2538.1

  81. v1.2537.1

  82. v1.2536.1

  83. v1.2535.1

  84. v1.2534.1

  85. v1.2533.1

  86. v1.2532.1

  87. v1.2530.1

  88. v1.2529.2

  89. v1.2529.1

  90. v1.2528.1

  91. v1.2527.1

  92. v1.2526.1

  93. v1.2525.1

  94. v1.2524.1

  95. v1.2523.2

  96. v1.2523.1

  97. v1.2522.1

  98. v1.2521.2

  99. v1.2521.1

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP/architecture-centertree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, learning-and-reference
Contributors61
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:architecture-center
JSON
/artifacts/architecture-center.json
MCP
Connecting an agent