Eighteen SharePoint components that run entirely inside your tenant. No backend. No Graph permissions. No migration. They read the lists and libraries you already have, however you already structured them.
The middle ground between out-of-the-box and custom development.
No list data, no documents, no Graph API data ever leaves your tenant. No backend database, no Graph permissions, no admin consent grants, no content telemetry — licensing is verified with only your domain and the product owner's email. And there are no feature exclusions in any cloud, including GCC.
Point a web part at a list and map its columns — Title, Image, Description, whatever they're actually called. No mandated column names, no required content types, no provisioning scripts, no migration. Your lists stay exactly as you built them.
Adopt one web part on one page. Keep every built-in web part you have. Nothing is ripped out, nothing is migrated — and removing Zenpo leaves your data exactly where it was: in your lists.
Every component is production-built, configured without code, and reads your existing SharePoint lists and libraries.
Icon + headline + text blocks, authored right in the web part — no list required.
Stacking Text and Image web parts by hand gets you close — never clean, never a unit.
The same blocks, populated from a list — content updates without editing the page.
The native path is hand-written JSON list formatting — and it breaks on Microsoft's updates.
In-page navigation that isn't the site's left rail — wayfinding for long pages.
SharePoint has site navigation; it has no in-page or section navigation web part at all.
Collapsible Q&A and FAQ sections, driven by a list or library.
Collapsible sections are page structure, not content — they can't be driven by a list.
Searchable, filterable people from a list — no Graph, no stale AD.
The native People web part is a hand-picked static list — no search, no filter.
Full-bleed rotating hero banners with per-banner links.
Auto-playing, full-bleed rotation the Hero web part's fixed tiles don't offer.
Mixed media and copy in a rotating frame, with calls to action per slide.
Image Gallery rotates, but carries no per-slide copy and no call to action.
Tabbed content panes inside a single page section.
No first-party Tabs web part exists. The workaround is stacking sections and hoping people scroll.
Animated KPI and metric tiles, fed from list data.
No first-party equivalent — numbers get typed into Text web parts and go stale the next day.
Documents, images and links, mixed in one filterable masonry grid.
Document Library caps at 30 files with one filter; Image Gallery can't mix documents and links at all.
Featured-item and call-to-action blocks with real design control.
A composed feature block, not a single button.
Chronological milestones, drawn from a list.
No first-party equivalent — milestones end up a static image or a bulleted list.
Compact multi-list calendar, colour-coded by configuration. On AppSource today →
The Events web part is agenda and tile only, single-source, with no colour coding.
Multi-timezone clocks for distributed teams. On AppSource today →
Same idea as the native World Clock — ours works.
Lean page layouts — structure only, nothing to strip, nothing provisioned.
Microsoft's templates arrive pre-filled with sample copy and stock imagery you delete before you can start.
A full org tree from a SharePoint list — no Entra dependency.
The built-in chart anchors to one person, can't export, excludes external users, and stops where Entra manager data is missing.
Birthdays and work anniversaries, with correct recurring-date logic.
The workaround is calculated columns plus JSON formatting — and the recurring-date maths is what goes wrong.
A full month view with multi-list overlay, recurrence and all-day events.
Classic SharePoint had colour-coded calendar overlays; modern lost them and never replaced them.
People Directory, Org Chart, and Birthdays and Anniversaries share one people list — one setup, three surfaces. Mini Calendar and Full Calendar run the same engine at two sizes.
If someone can edit a SharePoint page, they can use Zenpo — including on pages surfaced in Microsoft Teams. Any authorized team site can improve its own pages without asking a central intranet authority for permission.
No countdowns, no dated promises — we're building. Leave an email and we'll write exactly once, when the suite is available.