Knowledge · SharePoint Framework
What are SPFx webparts?
SPFx is short for SharePoint Framework — Microsoft's official development model for modern SharePoint experiences. An SPFx webpart is a ready-made building block your editors drop onto any page: an org chart, a news hub, a KPI dashboard.
- .sppkg file — nothing else gets installed
- 1
- .sppkg file — nothing else gets installed
- minutes from upload to first page
- <10
- minutes from upload to first page
- external servers, zero tracking
- 0
- external servers, zero tracking
- users, pages & sites per license
- ∞
- users, pages & sites per license
Everything on a SharePoint page is a webpart
Open any page of your intranet and look closely: The welcome text? A webpart. The news? A webpart. The quick links? One too. Modern SharePoint pages work like a construction kit — editors snap ready-made blocks into a grid, no code involved.
Microsoft ships about 40 stock blocks. They cover a lot — but not everything. An interactive org chart? A metrics dashboard with status lights? That's exactly where SPFx webparts come in: they extend the kit with the pieces Microsoft doesn't ship. To editors, they feel exactly like the built-in ones.
One file — and your whole tenant has it
An SPFx webpart ships as a single file: the SharePoint package, .sppkg for short. Your IT uploads it once to the app catalog, SharePoint's central app management. From then on, every site in your organization can use the webpart — from the executive portal to the shop-floor team site.
Updates travel the same road: upload the new file, SharePoint detects the higher version number, every page is current — settings stay intact. No per-machine installs, no rollout project, no license server.
Five terms you'll never have to look up again
- SPFx
- SharePoint Framework — Microsoft's official model for extending SharePoint. The standard since 2017, and still actively developed.
- .sppkg
- The package format for SPFx solutions. One file containing your complete webpart — all resources included.
- App catalog
- Your tenant's central app library. Anything published here becomes available to every site in your tenant.
- Tenant
- Your Microsoft 365 environment: users, sites, data. Our licenses are per tenant — not per user.
- Microsoft Graph
- Microsoft's official API for profiles, calendars, files and more. The only party our webparts ever talk to.
Secure, because nothing leaves your tenant
SPFx webparts run in the signed-in user's browser — inside your SharePoint environment, within its permissions, under its policies. What someone isn't allowed to see, the webpart won't show either.
Our webparts talk exclusively to Microsoft APIs. No external servers, no third-party CDNs, no tracking. If a webpart needs directory data, your admins must explicitly approve the permission first — nothing runs before that. Exactly the control SharePoint admins use to evaluate third-party solutions.
Buy or build?
SPFx development is real front-end engineering: Node.js, React, TypeScript, the SharePoint toolchain, theming, accessibility, Graph permissions. Doable? Absolutely. But run the numbers:
| Criterion | Build yourself | Buy ready-made |
|---|---|---|
| Time to production | 4–12 weeks of project time | Today — upload plus 10 minutes |
| Cost | Developer day rates × weeks | One-time price from €290 |
| Microsoft's SPFx updates | Your problem | 12 months included |
| Maintenance & bugfixes | Ongoing budget required | On us — included |
| Design & accessibility | Build and test yourself | Done, themeable, tested |
And if your requirement is truly specific? That's what our fixed-price custom webpart service is for — you describe, we build. Custom webpart
What teams are building with this right now
Common questions
Do I need developers to use an SPFx webpart?
No. Installation is a file upload to the app catalog that any SharePoint administrator completes in minutes. Our illustrated deployment guide walks you through step by step.
Do SPFx webparts work in Microsoft Teams?
Many do — SPFx also powers Teams tabs and personal apps. Each product page states whether the webpart supports Teams.
What about SharePoint on-premises (Server 2016/2019/SE)?
Our webparts are built and tested for SharePoint Online. On-premises farms only support older SPFx versions — get in touch if you need this.
How is buying here different from Microsoft AppSource?
AppSource cannot sell paid SPFx packages directly — which is why virtually every professional vendor sells webparts through their own store. You get the same standard .sppkg from us, complete with invoice, updates and support.