Service · Web development

Custom extranet development for customers, partners and suppliers.

A protected portal behind a login where external stakeholders view documents, follow statuses and work together. Multi-tenant, with SSO, audit log and branding per customer. Custom-built when Liferay or SharePoint are too coarse for your flow.

SSO & MFAMulti-tenantAudit logWhite-labelAPI access

An extranet is neither an intranet nor an open website.

An intranet serves your own employees. A public website serves anyone who comes along via Google. An extranet sits in between: a protected online environment for parties who do belong to your organisation but are not on your payroll. Customers, distribution partners, suppliers, agents, freelancers, referrers, dealers, trade association members, alumni: each with their own roles, their own flows and their own sensitivities. The UX has to be self-explanatory (your partners won't get an onboarding manual), the security has to be tighter than on a public site, and the branding matters even more because external parties read the portal as your brand.

Customer portal, partner portal, vendor portal and industry portal are all forms of the same concept. The label depends on who logs in, not on the underlying technology. Under the hood they share the same building blocks: authentication, multi-tenant data separation, role management, audit log, document vault, notifications and API access. What differs is the UX, the business flow and which systems you connect to it.

We build extranets for B2B companies with external stakeholders: insurers (policyholder and broker portals), banks and financiers, SaaS vendors, construction companies (client portal for ongoing projects), healthcare institutions (referrer portal), staffing agencies, law firms and notaries (case file portal), educational institutions (alumni environment) and energy companies (large-consumer portal). Always custom: not a standard Liferay template that half fits, but a portal that clicks with your workflow and your brand. For lighter cases we also combine this with headless CMS components via our web development practice; for more complex projects you're better served by enterprise software development as the backbone.

Three types of extranet we build.

The label differs per organisation and audience (customer portal, partner portal, vendor portal), but under the hood it is always the same extranet architecture. We will advise which variant fits in the first conversation.

Compact project · fixed sprint budget

Customer portal or self-service environment

A secure environment where your customers download invoices, create support tickets, manage account details, renew contracts and track statuses. Suited to SaaS vendors, insurers, telecom providers and energy companies that want to use self-service to take pressure off support. SSO via the customer's IdP or magic link for occasional users, with a light branding layer so the environment feels like part of your brand. Often also connected to your CRM and invoicing system so customers see their own status in real time. Related: employee portal for when you want to centralise internally rather than externally.

SSO + MFARole managementSelf-serviceNotifications
Mid-sized project · fixed sprint budget

Partner or distribution partner portal

For channel partners, distributors, dealers, agents or resellers who run their own business through your channel. A branded portal where partners configure products, place orders, view stock levels, download marketing assets and co-branded materials, register leads and track their pipeline. Multi-tenant so each partner only sees their own data, with granular permissions within a single tenant (a sales employee sees different data from a partner admin). Approval workflows for non-standard prices or large orders. On the purchasing side, you can set up a vendor portal in parallel so your suppliers also work through a secure environment.

Multi-tenantWhite-labelPunchOut/cXMLMarketing assets
Larger project · fixed sprint budget

Production extranet with deep integrations

A mission-critical extranet that exposes ERP, CRM, DMS, policy administration and e-signing all at once. Industry-specific flows for healthcare (referrer portal with NEN 7510), finance (DORA-compliant audit), energy (large-consumer portal with real-time meter data) or construction (client portal for ongoing projects with drawings, planning and invoicing in a single view). Multi-language and region-specific flows because your customers work in multiple countries. This often comes with a CIAM platform for federated identity across dozens of customer IdPs, plus granular consent management that demonstrably upholds GDPR rights.

ERP integrationMulti-languageFederated SSOAudit + DORA

What makes it technically an extranet.

Not every secure login page deserves the label extranet. Under the hood, a number of building blocks make the difference compared with an ordinary login page or a light CMS. We build them into almost every project:

Authentication and identity. Single sign-on via your IdP (Microsoft Entra, Google Workspace, Auth0, Keycloak) or federated SSO so external parties bring their own IdP. MFA on by default for admins, optional for users. Magic link for occasional users who don't want a permanent account. For government contact, we integrate eHerkenning or DigiD.

Multi-tenant data architecture. Each customer sees only their own data. Implemented via row-level security in PostgreSQL or MySQL, a schema per tenant, or a separate database per tenant, depending on your risk profile. For strictly confidential data (medical, financial) we often choose stronger isolation; for SaaS tenants with many small customers, row-level security with thorough testing is more common.

Granular permissions and audit log. Multiple roles within a single tenant are the norm: admin, user, viewer, external accountant. Every action (login, view, edit, export, delete) is logged to an audit table with a retention period of several years. For compliance-driven sectors this is a hard requirement; for other sectors it's reassuring peace of mind.

Document vault and communication. A secure place for documents with version management, watermarks on sensitive files and an audit log per file. In-app comments, mentions and notifications (email, push) mean communication no longer runs through scattered email threads, and the whole organisation can see whose turn it is.

Approval workflows and self-service. Four-eyes principle, escalations and delegation wherever your business needs them. Self-service for invoice downloads, support tickets, account management and GDPR rights, so your own team doesn't have to handle every request manually.

Branding, reporting and API. Branding per tenant (white-label) so trade associations can deliver their extranet under their own brand. Reporting and dashboards per tenant. API access for PunchOut/cXML in procurement, and webhooks for real-time integrations with ERP, CRM and invoicing.

What you get at the end.

A production-ready extranet plus everything around it to manage it yourself: codebase, documentation, training and an optional support contract.

  • Extranet production environment + stagingRuns in your cloud (GCP/AWS/Azure/Hetzner) or with us in a managed environment. Multi-tenant separation at row, schema or database level, depending on your security requirements.
  • Authentication layer with SSO and MFASetup of SAML, OIDC or OAuth towards your IdP. Federated login so customers and partners can bring their own Microsoft Entra or Google Workspace. MFA enabled by default for administrators.
  • Codebase + architecture documentFull source code in your own Git repository, build instructions, infrastructure-as-code and a readable architecture overview. No lock-in to a single supplier.
  • Audit log + GDPR control panelWho has viewed, changed or exported which data. Readable per tenant. GDPR rights flow built in (access, rectification, erasure) so you can respond to requests without custom work.
  • Admin guide and end-user trainingTwo sessions for your key users, a short video tutorial for external users and written runbooks for your IT team: adding roles, creating tenants, reading the audit log.
  • Support contract (optional)Monitoring, backups, security patches, dependency updates and ongoing development for a fixed monthly price. Four response-time levels, depending on how critical the extranet is to you.
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When a custom extranet is the right choice.

Not every extranet needs to be custom. For simple document sharing there are perfectly good standard platforms. We come into the picture when one of these patterns applies.

Document flows

Email is hitting its compliance limits

You send dozens of documents back and forth with customers or suppliers every week. Versions get lost, statuses are unclear, and your data protection officer points to the leak risk of business attachments.

Compliance

An audit trail is a hard requirement

Your sector (finance, healthcare, energy) demands demonstrable logging of who has seen or changed what. SharePoint-level audit logging is too coarse for that; you need per-record granularity with a retention period of several years.

Scalability

The number of external parties is growing

What was manageable by hand with a handful of partners doesn't scale to dozens or hundreds. Self-service onboarding, automated role management and multi-tenant separation become a necessity rather than a luxury.

Branding

White-label needed per customer

Trade associations, consulting firms and SaaS vendors want to deliver their extranet to customers under their own brand. Own domain, own colours, own logo per tenant, something standard platforms only partly support.

Integrations

Multiple systems at once

The extranet needs to pull data from ERP, policy administration, CRM and DMS, sometimes in real time. Standard portal templates then force you into duplicate data storage or fragile integrations; a custom layer avoids that.

Target group

Different types of users

One extranet serves policyholders and brokers, dealers and clients, referrers and patients alike. Each type sees its own view with its own permissions and its own UX, which isn't a standard out-of-the-box flow.

How an extranet project works.

1

Introduction and flow analysis

A conversation to understand which external parties need to work in the extranet, which flows they go through, which systems we need to connect and which compliance requirements apply. The result is a draft scope with assumptions that we test in the next step.

2

User research and scope

A workshop with your team plus interviews with a handful of external users — customers, partners or suppliers. By the end, you have clear personas, a role matrix, a first screen flow and a final scope. This is also where we define how multi-tenant data separation will work and which IdP integrations we build.

3

Building in sprints with early access

A working build in staging every two weeks. Your key users test along, as does a select group of external pilot users. After a few sprints, the MVP is up and running for the first tier — often the customer or partner side — and grows from there with a document vault, approval workflows, branding and the heavier integrations with ERP, CRM and invoicing.

4

Security, pentest and rollout

Before go-live, an external party carries out a pentest and we run a DPIA review, then roll out in phases to your customer or partner base. We start with a pilot group, monitor the support load, fine-tune where needed and then scale up. Training sessions for key users, video tutorials for everyone else. After that, ongoing maintenance covers security patches, dependency updates, monitoring and further development based on what your users tell us.

5

Management and further development

An extranet is not a project that is finished once it goes live. External parties change, IdPs get updated, compliance requirements shift and new integrations come along. We stay involved through a maintenance contract — patches, monitoring, smaller features — so we still know the codebase when you want a larger extension. No lock-in: the code lives in your own Git, and you can switch providers or take it in-house at any time.

Frequently asked questions.

What clients usually want to know before we start.

What is the difference between an extranet, an intranet and a customer portal?
An intranet is for your own employees — internal knowledge, HR, communication. An extranet is for parties outside your organisation who still belong to your business: customers, partners, suppliers, referrers. A customer portal is a specific type of extranet, aimed at one target group (your customers). The same goes for a partner portal and a vendor portal, for partners and suppliers respectively. Under the hood they share the same architecture — secure login, role management, audit log — but the UX, content and integrations differ per target group. If you actually want to build internally, take a look at our page on an employee portal.
Do you replace Liferay, SharePoint or Salesforce Experience Cloud?
Not by default. For large enterprise portals with hundreds of communities, Liferay DXP and Salesforce Experience Cloud are good choices — a lot comes out of the box. We come into the picture when those platforms are not flexible enough for your flow, are too heavy for your scale, or when you want to expose several systems at once through your own UX. For truly large, specialised projects with deep system integrations, you are sometimes better off with enterprise software development as a whole.
How is data separated between tenants in a multi-tenant extranet?
There are three models. Row-level means one database, one shared table, a tenant ID column on every row and row-level security policies in the database (PostgreSQL supports this natively), so queries are automatically restricted to the right tenant. Schema-level means one database with a separate schema per tenant: shared table definition, separate data. Database-level means a separate database per tenant, possibly even on separate servers. Which model fits depends on your security requirements, the number of tenants, your cost budget and how much customisation you need per tenant. For strictly confidential data (financial, medical, defence) we more often choose schema or database level, accepting the higher operational complexity. For SaaS providers with hundreds of small tenants, row-level is usually more practical and cheaper to scale, provided the test suite locks down that isolation rigorously. We work out the choice with you in the architecture phase, based on your risk profile.
How do you handle GDPR and compliance for a B2B extranet?
Several layers at once. Privacy by design in the architecture (data minimisation, encryption at rest and in transit), a DPIA for every major project, GDPR Art. 28 data processing agreements with sub-processors, and a built-in GDPR rights flow per tenant (access, rectification, erasure). For healthcare extranets we add NEN 7510 controls, for financial extranets DORA requirements, and we build publicly accessible B2C extranets to WCAG 2.2 AA in line with the European Accessibility Act. For the complete picture, see our page on a CIAM platform.
Are SSO and MFA mandatory for external users?
MFA is strongly recommended, and for us it is on by default for administrators and users with access to sensitive data. For external users it depends on your audience. Business partners often have their own IdP (Microsoft Entra, Google Workspace, Auth0, Keycloak), which we connect via SAML or OIDC federation, so they log in with their existing account and you don't have to manage passwords. Occasional users such as one-off clients, freelancers or patients often get a magic link plus optional TOTP, so they don't have to create an account for a single visit. We use iDIN, eHerkenning or DigiD where your audience expects it, for example in government contact, healthcare portals or financial services where identification is required by law. For the complete identity question, see our page on a CIAM platform.
Do you build a mobile app alongside the web extranet?
We can, but it isn't always necessary. We build the vast majority of extranets to be mobile-responsive: your customers and partners use them on a laptop or phone without installing anything, with a UX that works just as well on a narrow screen. A separate mobile app comes into play for field services (field engineers, an audit app for inspections), offline scenarios (poor connectivity, remote locations), push notifications as an important conversion driver, or a dedicated camera/scan flow. We advise case by case and can build both hybrid (React Native, Capacitor) and native (Swift/Kotlin). A project often starts with a strong responsive web extranet, and a lean mobile app is added later for specific flows.
What does a custom extranet cost?
An honest answer: it depends on scope, integrations, the number of roles and the level of compliance. A customer portal with SSO and a document vault sits at a very different end of the spectrum from a multi-tenant production extranet with an ERP integration, white-labelling and DORA requirements. Three variables weigh most heavily on the budget: the number of distinct roles and flows (each role is effectively a sub-product), the number of external systems the extranet has to talk to (each API integration costs analysis, build and monitoring), and the level of compliance (audit requirements, pen test, DPIA). We work with fixed sprint budgets, so there is no open-ended cost, and after the scoping phase we give you a substantiated range, including the assumptions that have the biggest impact on the price. For a broader picture of how we work, see our web development page.
Can we use a separate brand and domain for each client (white-label)?
Yes, and that is one of the reasons to choose a custom build. For each tenant we can link a separate subdomain or custom domain, its own colours, logo, favicon and even its own email templates. Trade associations and consulting firms use this to deliver their extranet to end clients under their own brand. This is not available out of the box on standard platforms, where you usually give up consistency.

Talk to us about your extranet.

A no-obligation introductory call of half an hour. We listen to your flow, ask follow-up questions about roles and compliance, and give you direction you can actually use, whether that points to a custom build, a standard platform or a hybrid.

Edit content