Your customers expect the cloud, your product was built for the desktop

Your customers have relied on your software for years to run critical parts of their business. It installs at each site, keeps a database per customer and connects to the printers, scanners and devices their work depends on.

Now they expect to reach it from anywhere, and your cloud-based competitors don't ask them to run a server. That doesn't mean rebuilding everything as SaaS. We help you decide what to keep, what to change and how far to move.

One of the first AWS SaaS Competency partners worldwide

AWS Partner SaaS Services Competency

Validated by AWS

We have held the competency since AWS launched it in 2020. It is checked against real customer delivery, not a training course, and covers SaaS architecture, tenant isolation, onboarding, operations and the migration of existing products to SaaS.

The AWS SaaS playbook

We use the migration patterns, tenancy models and SaaS Lens reviews AWS has developed with thousands of software companies, so your product moves along a path AWS recognises and supports.

Built to be run

Since 2005 we have built and run platforms for SaaS companies, ISVs and regulated software teams, so the design accounts for how your product will be operated after launch, not only how it is built.

The hard part is rarely the database

Years of business logic often sit inside the forms themselves, which is why every change to a complex form takes longer than it should. Our team, with the assistance of AI, can now analyse a codebase of millions of lines in days. This is work that used to take engineers months.

Start with a five-day assessment

A fixed-price Rapid Modernisation Assessment before you commit to a larger analysis or build.

  • Review your business case, code, tenancy, integrations and devices, security and identity, and hosting needs
  • An options paper and a recommended direction
  • Estimated effort, cost and time for each path together with risk profile.
  • A walk through with your team of the findings

Three paths to SaaS

We review each SaaS path against your code, data, integrations and customers. The recommendation may be one path or a sequence that starts with one and grows into another.

Silo first

Silo first. Each customer runs its own copy of the current application and database on AWS, behind shared SaaS foundations.

Each customer runs an isolated copy of your current application and database on AWS. It is the fastest route to SaaS with little change to the code, though running costs stay per customer.

Layered

Layered. A shared web tier and shared data serve every customer, while each customer keeps its own application tier.

Layers move to multi-tenancy one at a time, usually the web tier and the data first, while each customer keeps its own application tier. You gain shared infrastructure, central data and simpler updates, in exchange for running two delivery models for a period.

Re-platform

Re-platform. One multi-tenant web application on a shared business logic layer and shared data serves every customer.

The product is rebuilt as one multi-tenant web application on a business logic layer extracted from the existing code. It is the largest investment of the three and the only path that retires the desktop product entirely.

Hosting alone is not SaaS

Every path includes the shared services that turn hosted software into a SaaS product.

  • Tenant onboarding that provisions a new customer automatically
  • One identity and sign-in model across every customer
  • Tenant configuration held centrally instead of in each installation
  • Metering of what each customer uses, ready for pricing and cost decisions
  • Monitoring that shows the whole system and each customer within it
  • One release pipeline that updates every customer

After the assessment

Plan the rebuild

The full Modernisation Assessment goes deeper into the code, data, integrations, security and operations, and gives you a staged roadmap with fixed-price work packages for the first stage. The rapid assessment fee is credited against it.

Rebuild on a running system

Where it fits, the current product moves onto AWS first so new customers start in the cloud straight away. The business rules are then pulled out of the screens and proven against the existing product before the new web application is built on them.

Run your product as a service

You receive documentation and a handover, or choose 24/7 managed operations through Cloud Management with agreed support responsibilities.

Audited and certified

AWS SaaS Competency AWS SaaS Competency
ISO 27001 Certified ISO 27001
AWS Advanced Partner AWS DevOps Competency

Frequently asked questions

Do we have to rewrite the whole product?

No. Many products stay on the silo or layered path for years. A rebuild is only worth starting when the business case supports it, and the assessment tells you whether it does.

What happens to our development team?

They stay central to it. Your developers know the business rules better than anyone, and they work alongside our engineers to confirm the logic layer behaves correctly before anything changes for customers. They finish with a modern codebase and release pipelines they can keep building on.

What happens to devices at each customer site?

Printers, scanners, payment terminals and diagnostic devices usually connect through a small local connector at each site, which talks securely to your product on AWS. The assessment shows which of your devices and integrations need one.

Which technologies do you work with?

Most long-lived stacks, including .NET Framework, Visual Basic, Java, Delphi, PowerBuilder, PHP, Perl, Python, Ruby and ColdFusion, on databases such as SQL Server, Oracle, MySQL, PostgreSQL and Microsoft Access. We also take in the reporting, update and background services around them. The rebuilt product runs as a web application in your AWS accounts.

Can you help if we work in a regulated industry?

Yes. We flag the obligations for holding regulated data in the cloud, including residency, identity, access control and audit. base2Services is ISO 27001 certified and works with software companies in regulated industries.

Should we be single-tenant or multi-tenant?

Most SaaS products sit somewhere between the two. AWS describes the range as silo, bridge and pool models, from a dedicated environment per customer to fully shared infrastructure. Single-tenant keeps isolation simple at a higher cost to run and update; multi-tenant lowers running cost and speeds up delivery but needs isolation designed into the data, security and code. Many products offer both, with dedicated environments for the customers who need them.