The gap between what is there and what most businesses use

Picture a small business that has a WordPress website. They use it for their homepage, a services page, and a contact form. The database has a handful of posts in it. The user authentication system has one or two accounts. The REST API has never been called.

That same business is paying A$150 to A$500 a month in SaaS subscriptions. A CRM that manages their contacts. A task tracker for their team. An invoicing app. Maybe a staff directory. Each on a different server. Different logins. Different monthly bills. Different companies to deal with when something breaks.

The WordPress install that is already paid for could be running all of those things. It has everything it needs.

What is inside every WordPress install
  • MySQL database (can hold millions of records)
  • User authentication with roles and permissions
  • File upload and storage
  • Outbound email system
  • REST API
  • Plugin architecture for extending anything
  • PHP runtime environment
What most businesses use it for
  • Homepage
  • Services or about page
  • Contact form
  • Occasionally a blog post

What Merebase builds on top of what is already there

Merebase builds business applications that run on your existing WordPress install. The app lives at /mb/ on your site. Your team logs in with the credentials they already have. Your data goes into your database on your server. No second hosting account. No additional login. No SaaS subscription.

These are not plugins. A plugin extends WordPress. A Merebase app is a separate application that uses WordPress as its infrastructure. It has its own data model, its own interface, its own logic. WordPress provides the server, the database, and the user system. The app provides everything else.

Job tracker
Log jobs, assign staff, track status, record sign off. Replaces a spreadsheet or a SaaS field service app.
CRM
Contacts, organisations, notes, follow-up tasks, pipeline stages. The two or three things you actually open a CRM to do.
Invoicing tracker
Create invoices, track what is sent, record what is paid. View what is outstanding. No accounting platform required.
Staff directory
Staff records, roles, contact details, documents, leave tracking. Internal access only.
Inventory counter
Track stock levels across locations. Log movements. Alert when a threshold is hit. Replaces a shared spreadsheet.
Custom dashboard
Pull data from your own database into a single view. The two or three numbers your team checks every morning.

Each app is built to a scope you agreed to before any money changed hands. A$499 once. Build preview in 3 to 5 working days. The code is yours.

One login. One server. One data set.

The business case is simple. You are already paying for the hosting. The infrastructure is already there. Adding a Merebase app to your WordPress install does not require a new server, a new database, or a new login system.

Your team accesses the app at /mb/ on your existing site. They log in with the same credentials they use for anything else on your WordPress install. Their access level is controlled by their role. An editor can use the app. An administrator can configure it. A subscriber sees only what they are supposed to see.

Your data stays on your server. Not on a SaaS company's server in another country. Not subject to a terms of service change. Not accessible to anyone except the people you give access to.

WordPress is not just what your website runs on. It is the foundation your business apps could be running on too.

This is what we think WordPress could be

WordPress has been used almost exclusively as a content management system since it launched in 2003. That reputation is deserved. It is very good at publishing content. But it is not all it can do.

The infrastructure underneath WordPress is general purpose. A PHP server with a MySQL database, a user system, and a REST API can run almost any web application. The website is just one application that happens to use those components. A business app is another.

Most of the hundreds of millions of WordPress installs in the world are running websites that use a fraction of the available infrastructure. The businesses behind those installs are paying for SaaS subscriptions to fill the gap. Merebase closes that gap by building the apps that should have been there all along.

This is not a niche insight. It is a straightforward observation about how much capability already exists in most businesses and how little of it is being used.

Frequently asked questions

What kind of business apps can run on a WordPress install?
Job trackers, CRM systems, invoicing apps, staff directories, inventory counters, custom dashboards, document tracking systems, and most other internal business tools. If the core job is managing records, tracking status, or producing outputs like invoices, it can run on WordPress. The limiting factor is not WordPress. It is whether the job fits a A$499 scope.
Do I need a developer to add a business app to my WordPress site?
No. A build architect scopes the app. Merebase builds it. It is delivered as a zip file you upload in WP Admin. The install takes under five minutes. Your team accesses it at /mb/ using the logins they already have. No developer needed after delivery.
Is it safe to run business data on a WordPress install?
Yes, with the right configuration. Merebase Core includes security hardening settings out of the box: login URL renaming to reduce automated attacks, and REST API restriction so unauthenticated users cannot enumerate your site structure. Your data stays on your server, not on Merebase's servers.
What happens to my existing WordPress content if I add a Merebase app?
Nothing changes. Merebase apps live at /mb/ on your install. Your homepage, your pages, your theme, and your existing content are completely untouched. The app and your website run alongside each other on the same server without interfering.