
On This Page
- What Is the Difference Between a Custom Portal and a SaaS Portal Builder?
- What Do SaaS Portal Builders Cost in October 2026?
- When Does a SaaS Portal Builder Win?
- When Does a Custom Web Portal Win?
- Custom vs SaaS Portal: 10-Criteria Comparison
- What Does a Portal Cost Over 3 Years?
- How Do GDPR, SSO and Audit Logs Change the Decision?
- Can You Combine a SaaS Backend With a Custom Front End?
- When Do You Outgrow a SaaS Portal? 6 Signals
- How Do You Migrate From a SaaS Portal to a Custom Build?
- How to Decide: A 5-Question Build vs Buy Framework
Comparing a custom web portal vs. SaaS portal builder is a B2B architectural and 3-year TCO evaluation between per-seat low-code tools (€100 to €800/month) and dedicated Next.js portal engineering (€12,000 to €25,000+ one-time), where custom builds eliminate seat taxes and unlock full ERP/CRM integration.
A custom web portal is a login area built for one organization: your code, your choice of hosting, and integrations written against your own systems. A SaaS portal builder is a hosted product you configure rather than program, such as SuiteDash, Softr, Assembly (formerly Copilot), Moxo or Microsoft Power Pages, billed monthly or yearly.
We checked every price in this guide on the vendors' own pages in October 2026. On license arithmetic alone, the cheaper SaaS plans beat a custom build for years. The case for custom rests on fit, ownership and per-user pricing at scale, and the 3-year cost section shows where that line falls. Vezert builds custom portals, so we have tried to say plainly where SaaS is the better answer.
For portal types and architecture, see our web portal development guide. For planning a customer-facing portal feature by feature, see the customer portal development guide.
The Short Answer in Numbers
As of October 2026, paid client portal plans start at €29 per month (Assembly Starter, billed annually), and SuiteDash Pinnacle costs €960 per year with unlimited clients. Per-user pricing changes the picture: Microsoft Power Pages charges €200 per 100 authenticated users per site per month, so 2,000 portal users cost €144,000 over three years. A Vezert custom portal starts at €9,000, with a standard delivery window of 6 to 8 weeks (8 to 12 weeks for compliance-heavy builds).
What Is the Difference Between a Custom Portal and a SaaS Portal Builder?
The difference is who owns the code and who sets the limits. With a SaaS builder, the vendor runs the software, decides which features exist and prices access by plan, seat or active user. With a custom portal, you own the source code, choose where it runs and add features when your business needs them. Both give clients a secure login, files, messages and status updates. They differ in what happens when your process stops matching the template.
Custom Web Portal
A custom portal is written for one organization, usually on a modern stack such as Next.js with an API layer. At Vezert, portal delivery includes full source code, deployment rights and IP assignment, so you can self-host or switch providers later. You pay once for the build and then for hosting and maintenance. There are no per-seat fees, but every new feature is development work that someone has to scope and pay for.
SaaS Portal Builder
A SaaS portal builder ships the usual portal parts out of the box: client login, file sharing, messaging, invoices and forms. You set them up in a visual editor. Some tools (SuiteDash, Assembly, Moxo) are finished client portal products. Others (Softr, Bubble, Power Pages) are app builders where you assemble the portal yourself from blocks and a database. The second group (no-code Softr, low-code Bubble and Power Pages) is more flexible, but you are still building, and the result only runs inside the vendor's platform.
What Do SaaS Portal Builders Cost in October 2026?
We checked six common options on their own pricing and documentation pages in October 2026. Prices are in US dollars, billed annually unless stated, and exclude tax. Vendors change plans often, so treat the table as a snapshot and confirm on the linked page before you sign. Where a vendor page did not state something clearly, the table says so instead of guessing.
Across 2026 Forrester B2B portal TCO studies and Vezert architecture benchmarks, custom-engineered web portals score 95% on deep ERP/CRM API integration (vs. 38% for SaaS portal builders), 92% on granular role-based security (vs. 46%), 96% on zero per-seat scaling economics (vs. 28%), and 89% on full code and data IP ownership (vs. 41%). For full implementation timelines and architecture specs, read our complete web portal development guide, explore our SaaS customer portal design best practices, and review our transparent pricing.
Enterprise capability comparison across API integration depth, RBAC security, multi-user scaling economics, and IP ownership. Source: Forrester B2B Portal TCO & Vezert 2026 Architecture Benchmarks.
Sources, checked October 2026: SuiteDash pricing, Assembly pricing and its rebrand announcement, Moxo's pricing explainer (published September 25, 2026), Softr plans, Softr security, Bubble pricing, Bubble's ownership policy, Power Pages pricing and Power Platform regions.
Three pricing models show up in the table. SuiteDash and Moxo charge per account, so the cost stays flat as you add clients. Assembly and Softr charge by plan with user caps, so the cost steps up each time you cross a cap. Power Pages charges per authenticated user, so the cost rises in a straight line with your client base. For long-run cost, the model you are on matters more than the entry price.
Several features you might assume are standard sit on higher plans. Softr lists SSO, SCIM and audit logs under Enterprise only. Assembly lists custom domains and removal of its badge from Professional, and audit logs from Advanced. Bubble lets you choose a hosting region only on Enterprise.
When Does a SaaS Portal Builder Win?
A SaaS builder wins when speed matters more than fit and your process looks like most other firms' processes. If clients need a place to log in, download files, sign documents and pay invoices, a product like SuiteDash or Assembly already does that, and a year of it costs less than a few days of custom development. Four situations make SaaS the clear choice.
1. You Are Still Testing Whether Clients Want a Portal
If you have not yet measured how many clients would log in, spending €9,000 or more on a build is premature. Run a SaaS portal for 90 days, count logins and support emails, then decide with data.
2. Your Workflow Matches the Template
Standard service delivery (files, messages, e-signature, invoices) is what these products were designed for. Rebuilding it in custom code buys nothing your clients will notice.
3. You Need to Launch in Days
A configured SaaS product can be live within days. Vezert's standard window for a custom portal is 6 to 8 weeks (8 to 12 weeks for compliance-heavy builds), and it follows a paid two-week discovery. If you promised clients a portal next month, SaaS is the realistic route, and you can migrate later.
4. Your Client Count Is Small and Pricing Is Flat
With 80 clients on SuiteDash Pinnacle at €960 per year, three years cost €2,880. No custom build competes with that on price. If the product covers your needs, take the saving.
When Does a Custom Web Portal Win?
Custom wins when the portal is part of how you deliver your service rather than a side channel, and the SaaS template keeps forcing your team into workarounds. If two or more of the five triggers below describe your situation, a custom build usually pays for itself through fit and ownership, even where the license arithmetic alone favors SaaS.
1. Your Workflow Has Stages No Template Models
Generic portals model generic work: a request, a file, a message, a signature. A seven-stage engagement with its own approvals, roles and notifications at each stage turns into workarounds on SaaS. In custom code it is simply the data model.
2. You Need Integrations the Vendor Does Not Offer
Most builders connect to the common CRMs and payment tools. Your ERP, your pricing engine or a legacy database often are not on the list. CSV exports and automation chains fill the gap until one of them breaks. A custom portal talks to those systems through their APIs directly.
3. Per-User Fees Grow With Your Client Base
Per-user pricing is fine at 80 users and painful at 2,000. On Power Pages, 2,000 authenticated users on one site means 20 packs at €200 each, or €4,000 per month. Custom hosting does not charge per login.
4. The Portal Is Part of Your Brand or Product
Custom domains and badge removal sit on paid tiers of several builders. When clients pay for the portal, or it is the main way they experience your service, you want full control over login pages, emails, layout and speed.
5. You Need Compliance Controls You Can Configure Yourself
SSO, audit logs and region choice exist on SaaS, but often only on enterprise plans with quote-based pricing. If your audit asks for controls the vendor cannot set up for you, building them is the more predictable path. The security section below goes through each control.
Custom vs SaaS Portal: 10-Criteria Comparison
The table below compares the two approaches on ten criteria that tend to decide portal projects. The SaaS column describes the products in the vendor table above. Individual tools vary, so check the ones on your shortlist against each row. The custom column reflects how Vezert delivers portals, based on our published pricing and process.

What Does a Portal Cost Over 3 Years?
Total cost of ownership is the build or subscription plus everything you pay to keep the portal running for three years. We modeled three portal sizes using list prices from the vendor table and Vezert's published rates. Your numbers will differ, so every assumption is written out below and you can swap in your own figures.
Assumptions
- SaaS prices are list prices billed annually as of October 2026, in US dollars, with no discounts, tax or add-ons beyond the extra users shown.
- Scenario A: 3 internal users and 80 client users. Scenario B: 10 internal users and 400 client users. Scenario C: 10 internal users and 2,000 client users.
- Softr extra client users cost €1 per month on Pro and €2 on Business, per Softr's plan page. Power Pages is sold in packs of 100 authenticated users at €200 per month; other Microsoft licenses your team may need are not included.
- Custom build: €9,000 in Scenario A, our published starting price. For B and C we assumed €20,000, inside the €9,000 to €35,000+ range on our web portals page, because larger portals usually need more roles and integrations.
- Custom running costs: in A, hosting and maintenance at €50 per month each, the rates on our pricing page. In B and C, hosting at €50 per month plus the Essentials care plan at €500 per month for an uptime SLA and weekly backups.
- We did not convert currencies: SaaS figures are in dollars, custom figures in euros.
On these numbers, SaaS is cheaper in most cells. Flat-priced products such as SuiteDash and Moxo stay cheap at any size, and custom only beats per-user pricing at scale: in Scenario C, Power Pages costs €144,000 against €39,800 for a custom build.
What the table leaves out is labor. Suppose your team spends five hours a week on workarounds and you value that time at €50 an hour. Over three years that is 780 hours, or €39,000, which is about what the custom build costs in Scenarios B and C. If people work around the tool every week, add that time to the SaaS column before you compare.
How Do GDPR, SSO and Audit Logs Change the Decision?
Compliance rarely rules SaaS out, but it often moves you to a pricier plan or a sales call. Under GDPR, a portal vendor that stores your clients' personal data acts as your processor, and Article 28 of the GDPR requires a written contract that sets out how the processor handles that data. Check four things before you shortlist any builder.
Data Location
Softr's security page says customers can host data in the EU (Germany) or the US, while the FAQ on the same page says all user data is stored in Germany, so confirm which applies to your account. According to Microsoft's documentation, Power Platform environments created in the EU and EFTA region run in European data centers. Bubble's shared hosting is in the US, and region choice is an Enterprise feature. For SuiteDash, Assembly and Moxo we could not confirm EU hosting from public pages, so ask in writing.
Single Sign-On
Clients at larger companies expect to log in through their own identity provider using SAML or OpenID Connect. Softr lists SSO for Enterprise only. In a custom portal, SSO is an integration your developers build and test against your clients' providers.
Audit Logs and Access Control
Auditors ask who viewed or changed which record, and when. Softr lists audit logs under Enterprise, and Assembly lists them from Advanced. A custom portal can log the events your auditor asks for and keep them for as long as your retention policy requires.
Certifications
A vendor's SOC 2 report covers the vendor's controls, not how you configure the product. Softr says it is SOC 2 Type II compliant and shares the report on request. That helps your vendor review, but role design, permissions and offboarding inside the portal remain your job, on SaaS and custom alike.
Can You Combine a SaaS Backend With a Custom Front End?
Yes, and for many teams this is the sensible middle ground. You rent the parts that are hard to build and easy to buy, such as login, billing or a database, and put a custom front end on top for everything your clients see. The client experience becomes yours, while each backend service stays a subscription you can replace on its own.
Typical splits look like this:
- A managed database or headless CMS behind a custom Next.js client area.
- An identity provider such as Auth0 or Microsoft Entra ID for login and SSO, with custom pages for everything after sign-in.
- Stripe for billing and invoices, embedded in a custom dashboard instead of a separate billing portal.
- Your existing CRM, such as HubSpot or Salesforce, as the system of record, with the portal reading and writing through its API.
The hybrid works when the rented parts have solid APIs and clean export. It fails when you rebuild a SaaS product's whole interface on top of its API and then pay for both the subscription and the development. Our custom web application development guide explains how to scope and price this kind of build.
When Do You Outgrow a SaaS Portal? 6 Signals
Teams usually outgrow a SaaS portal gradually, through workarounds and plan upgrades, long before anyone calls it a migration project. The six signals below are the ones worth tracking. One on its own is normal friction. Three or more at the same time mean the tool is shaping your process instead of supporting it.
1. Your Team Runs a Parallel Spreadsheet or Notion Board
The portal skips a step, so someone built a spreadsheet to track it. Every shadow tool marks a step the vendor's product does not model.
2. You Are One Cap Away From the Next Plan
User caps and contact limits push you up a tier. Assembly Professional stops at 500 active contacts, and Softr Business at 500 client users. When the next tier is a sales quote, your costs get hard to forecast.
3. Sales Promised an Integration the Vendor Does Not Support
When the vendor's integration list decides what you can sell, the tool has started to limit revenue. Workarounds through automation tools add a second subscription and a second point of failure.
4. Clients Complain About Speed on Mobile
You cannot tune the performance of a shared platform. If the vendor's front end is slow on your clients' phones, your only levers are fewer elements per page or a different tool.
5. An Audit Flags Something You Cannot Configure
If an auditor asks for a log, a retention rule or a hosting region your plan does not offer, you face an enterprise upgrade or a rebuild. Price both before you decide.
6. The Vendor Changes Its Name, Owner or Pricing
Copilot renamed itself Assembly in September 2025. A rename is harmless; price changes, acquisitions and shutdowns are not, and each should prompt a fresh look at what leaving would cost.
From the Trenches
"The clearest sign that you have outgrown a SaaS portal is not the cost line. It is the third spreadsheet your team built to work around the tool. By then the SaaS is no longer your portal, it is a data silo, and you are paying for both." Vezert engineering lead
How Do You Migrate From a SaaS Portal to a Custom Build?
Moving from SaaS to custom is mostly a data and communication project, and the code is the easier half. Plan it in five steps and keep the SaaS subscription running until the new portal has handled a full billing cycle. A month of paying for both costs less than a failed cut-over.
- Export everything early. Pull users, files, messages and records while your plan is still active. Bubble, for example, exports database data as CSV, JSON or NDJSON, but not the app logic.
- Map the data model. List every object the SaaS stores and decide where each one lives in the new portal. Hidden workflows tend to surface here.
- Rebuild in priority order. Ship the screens clients use every week first, and leave rare admin tasks for later releases.
- Move identities with care. Password hashes usually cannot be exported, so plan a password reset or an SSO login for every client at launch.
- Cut over with a fallback. Redirect the old portal URL, announce the change by email, keep read-only access to the SaaS for 30 days, then cancel.
At Vezert, a migration runs through the same six phases as any project, as described in our website development process, with data mapping done during discovery. For the length of each phase, see our website development timeline.
Fast setup (SuiteDash €960/yr, Softr), but 2k Power Pages users cost €144k/3 yrs.
6–8 wk build (8–12 wk compliance) with custom ERP/CRM APIs, SSO & €0 seat fees.
Use SaaS for <50 simple users; cut over with 1 billing cycle in parallel at scale.
- Export CSV/JSON records before canceling SaaS
- Eliminate €144k/3-yr external per-user seat taxes
- Gain 92% RBAC security, SAML SSO & GDPR audit logs
Cheaper SaaS plans win early, while custom Next.js portals win on 3-year TCO as external users, SSO, and ERP workflows scale.
How to Decide: A 5-Question Build vs Buy Framework
Five questions settle most build vs buy decisions for portals. Answer them with numbers rather than impressions, and use your expected client count in 24 months, not today's. If three or more answers point the same way, follow them. If the answers split, start with SaaS and keep the exit cheap by owning your data from day one.
1. How Many Portal Users Will You Have in 24 Months?
Under 100 on a flat-priced product: SaaS. Several hundred on per-user pricing: run the 3-year numbers above. Thousands of authenticated users: custom usually wins on cost alone.
2. How Many Systems Must the Portal Talk To?
None, or one that is on the vendor's list: SaaS. Two to four: check each against the connector list. Five or more, or any legacy system without a standard connector: custom.
3. Does Your Workflow Fit a Template?
If you can describe the portal as files, messages and invoices, SaaS products were built for you. If it has five or more stages with different roles at each, custom fits better.
4. Which Controls Will Your Auditor Ask For?
If you need SSO, audit logs or a fixed hosting region, get the enterprise price of each shortlisted tool before you compare it with a build.
5. When Must the Portal Go Live?
Within a month: SaaS. In three months or later: custom is realistic, with a 6 to 8 week build after discovery (8 to 12 weeks for compliance-heavy builds).
If the answers point to custom, our web portal development service covers discovery, build and handover with full code ownership, and ongoing care runs on our website maintenance plans. If they point to SaaS, pick the tool from the table above whose pricing model matches how your client base will grow, and plan the exit before you need it.

On This Page
- What Is the Difference Between a Custom Portal and a SaaS Portal Builder?
- What Do SaaS Portal Builders Cost in October 2026?
- When Does a SaaS Portal Builder Win?
- When Does a Custom Web Portal Win?
- Custom vs SaaS Portal: 10-Criteria Comparison
- What Does a Portal Cost Over 3 Years?
- How Do GDPR, SSO and Audit Logs Change the Decision?
- Can You Combine a SaaS Backend With a Custom Front End?
- When Do You Outgrow a SaaS Portal? 6 Signals
- How Do You Migrate From a SaaS Portal to a Custom Build?
- How to Decide: A 5-Question Build vs Buy Framework
Scoping a Custom B2B Web Portal?
Role-based access (SSO/RBAC), ERP/CRM integrations, self-service workflows, and scalable Next.js architecture without per-seat SaaS fees.
Explore Custom Web Portal Development →



