Diagram template
Hub: isometric central drum
MaxOne plinth seen corner-on carries a central drum with the hub's title and description on its round front and an optional icon on its roof; four to eight low tablets stand in two columns either side, each joined to the drum by its own channel cut into the plinth and carrying its title, optional icon and one-line role on its front face.
Categories
Included in
Max
When to use it
For a core platform, team or offer and the four to eight parts that each depend on it directly, such as the services on a shared data platform, the departments around a customer team, the channels fed by one campaign, or the partners around a core product. Each satellite states its own role toward the hub. Tablet positions and channel lengths are schematic: they show direct association, not sequence, rank or quantity. Not for links between satellites, more than eight parts or long descriptions.
Adjust after generating
Change the style, colors, and font, and these options, as often as you like without spending credits.
- Typography
- Spacing
What you fill in
Describe your topic in plain words and the AI fills these in. You can edit every field afterwards.
- Hub
- Title, description, and optional icon
- Satellites
- 4 to 8, each with title, description, and optional icon
Related templates
All hub & spoke templates
Architecture: system contextA C4 system context diagram, a "who uses it and what it depends on" slide, or an integration overview: one system, one to four actors that use it, and one to five external systems it calls or that call it, each link saying what it does.
Architecture: event hubEvent flows through one broker, bus, or topic hub with one to five producers and one to five consumers, such as Kafka topics, Google Pub/Sub, SNS fanning out to SQS queues, EventBridge rules, or a webhook gateway delivering to several handlers; built for fan-in and fan-out.
Framework: hexagonal prism clusterCapabilities around a core offer, skills around a team's purpose, services around a platform or workstreams around a programme goal, where which parts sit next to each other matters.
Framework: quarter ringOffer design with demand and delivery; Programme inputs and outcomes; Partnership contribution and support.
Framework: ring sectorsFor one supplied choice among three or four considered options with a single statement about the selected one: a target audience and its positioning, a pilot region and why it goes first, a shortlisted vendor and the deciding reason, or a chosen scenario and its premise.
Framework: shared source fanFor one shared basis adapted per branch: an offer tailored to audiences with their channels, a platform packaged into tiers with their prices, a policy applied per region with its owner, or a curriculum adapted per cohort with its format.