Category: Tech Insight

What Twenty Years of Building Booking Software Has Taught Us

MIDAS 20 YEAR ANNIVERSARY

We hear a version of the same story more often than you’d think: an organization gets in touch because their current booking system is going away. Sometimes the vendor got acquired and folded into a bigger platform. Sometimes a “free” tool they’d come to depend on quietly shut down. Sometimes a school management system swallowed the booking module they liked and replaced it with one they didn’t.

Whatever the cause, the result is the same – a business manager or facilities coordinator staring down a migration they didn’t ask for, hoping the data export comes out clean.

We’ve been building MIDAS since 2006, and stories like that are a big part of why we still are. So we wanted to write plainly about what we think actually matters when you’re choosing software that a school, a church, or a community group is going to depend on for years, not months – and where we think MIDAS earns its place.

The deployment question nobody else lets you ask

Almost every booking system on the market today makes one decision for you before you’ve even seen a demo: it will live on someone else’s servers, in someone else’s cloud, under someone else’s terms. For a lot of organizations that’s completely fine. For a lot of others – schools with strict data protection obligations, churches wary of where congregation data ends up, government bodies with procurement rules that basically require it – that’s a non-starter.

MIDAS is one of the few systems left that genuinely lets you choose.

Run it on your own server, behind your own firewall, backed up on your own schedule, and your booking data never has to leave the building. Or let us host it, if server maintenance isn’t something you want on your plate. Either way works, and – this is the part people are often surprised by – you can move between the two later if your circumstances change. Most vendors only built one option, so they don’t offer that choice at all.

Why “since 2006” is actually a selling point

Here’s a number that we think says more about MIDAS than any feature list could: the median organization using MIDAS today has been with us for over nine years. Not nine months. Nine years.

We bring this up not to boast but because we think it answers the real question underneath “which software should we buy?” – which is really “will this still be here, and will it still work, in five years?

A lot of the room booking space right now is genuinely unstable: companies get bought, folded into bigger suites, sunset, rebranded, repriced. MIDAS has been continuously developed since 2006, and we’re not trying to get acquired or chasing a quarterly roadmap review that might decide room booking is no longer “core.” It’s the whole business, and it has been for twenty years.

Pricing that doesn’t need a phone call to understand

Plenty of software in this space keeps its pricing behind a “contact sales” button – in fact in our own research we found that almost a third of software vendors don’t publish pricing – and we’ve never liked that as an approach.

So MIDAS doesn’t work that way. Every price is published, openly, on our website, based on exactly two things – how many venues you need and how many users you need. No per-booking charges that punish you for actually using the software. No mystery enterprise tier that only reveals itself after a demo. You can work out your exact cost in about thirty seconds, and when it’s time to renew, the price is the same standard rate you already know (subject to currency fluctuations), not some number that’s crept up while you weren’t looking.

If you’re the person who has to justify a line item to a board, a council, or a budget committee, that kind of transparency tends to matter more than people expect.

We’re not trying to be everything

This one took us a while to say plainly, so let’s just say it: MIDAS is not a church management system. It’s not a school information system. It’s not a facilities maintenance platform. If what you actually need is one giant piece of software that handles giving, attendance, gradebooks, and work orders as well as room bookings, there are products built for exactly that, and we’d rather tell you that upfront than pretend otherwise.

What we have noticed, though, is that booking is usually the thing those all-in-one systems treat as an afterthought – a module maintained alongside features that matter more to the wider platform. The organizations that come to MIDAS from a bundled suite tend to say some version of the same thing: booking finally works the way they need it to, and everything else they were using keeps doing its job right alongside it. MIDAS is built to integrate with the tools you already run, not to replace them.

If any of this sounds familiar

Maybe your team is juggling a shared calendar and a spreadsheet of “who’s using the hall Thursday.” Maybe you’re facing a migration because a system you relied on is being discontinued or absorbed elsewhere. Maybe you just want to know, in plain numbers, what a proper booking system would actually cost your organization.

Either way, there’s no obligation to talk to anyone first. Try MIDAS free for 30 days with your own rooms and your own schedule, or just look up your exact price right now.

Start your free 30-day trial – no credit card required.

See pricing for your organization – published openly, no sales call needed.


Security Enhancements in MIDAS v4.42

Security Enhancements

MIDAS v4.42 brings several important security enhancements. Here’s what’s changed and why it matters.

Argon2id now the preferred method of password hashing

For many years MIDAS has utilized “bcrypt” to store password hashes. While “bcrypt” is still accepted industry practice, newer encryption methods like “Argon2id” offer improved protection.

“bcrypt” is computationally expensive. This means it takes a significant amount of processing time to compute each password hash. bcrypt also includes a configurable “work factor” controlling how “computationally expensive” each calculation is.

Back in 2017, a “work factor” of 10 was widely considered by security experts to be sufficient at the time, and this is the factor we used in MIDAS.

By 2020, computing power had evolved and so “best practice” was to upgrade to a “work factor” of 12, which we transparently rolled out to MIDAS for our v4.25 update that year.

Now in 2026, we’re firmly in the quantum computing and AI age. While bcrypt is still considered secure, it is only “computationally expensive” from a processing (CPU) perspective.

Newer methods, like “Argon2id”, are both processor-intensive and memory-intensive, and so offer an even greater line of defense against brute-forcing password hashes.

We’ve implemented Argon2id for MIDAS v4.42. End users won’t see any difference, but password hashes stored in each MIDAS system’s database are now more secure than ever, and will be automatically updated the first time a user signs in to v4.42.

Self-Hosted customers: You’ll need to install the Perl module “Crypt::Argon2” if you wish to take advantage of this security enhancement. If this module isn’t available on your server, MIDAS will fall back to using bcrypt.

Option to sign out a user everywhere when maximum number of failed sign-in attempts reached

One of the existing security features in MIDAS is the ability for the software to automatically ‘lock’ accounts after a configurable number of failed sign-in attempts. Account access can then be quickly restored by an administrative user, or via a link that MIDAS will email to you if your account becomes locked in this way.

An account becoming ‘locked’ due to a high number of failed sign-in attempts prevents further sign-in attempts being made on that account. Until now, any existing active sessions that the user may have were allowed to continue unaffected.

For MIDAS v4.42, we’ve introduced a new security setting (found under MIDAS Admin Options → Security) that, if enabled and a user account becomes automatically ‘locked’ due to a high number of failed sign-in attempts, all active sessions for that account will be automatically terminated as well.

Suspending a user account instantly expires all active sessions for the user

If an administrator manually suspends a user account, MIDAS will now also expire all active sessions for that user. Previously, if an account was manually suspended, it wouldn’t affect any currently active sessions — now it does.

Security Fixes

We’ve also addressed a handful of security and account-related bugs for v4.42 which were discovered by our team…

Fixed: Possible to bypass forced password expiry

One of the “legacy” settings in MIDAS is the ability for administrators to routinely force users to change their password. Enabling this option isn’t something that we recommend. Indeed, this is considered bad practice, as forcing users to regularly change their passwords actually harms rather than improves security.

Despite that, some organizations still insist on routine password change policies, and therefore, we’ve had to retain this option in MIDAS.

MIDAS v4.42 fixes a small issue related to this, whereby since v4.39, if a user is forced to change their password due to it having expired, the user could easily bypass this requirement by simply hitting reload/refresh in their browser when prompted to set a new password. We’ve resolved this for v4.42.

Fixed: Weak passwords were allowed when passwords were reset

MIDAS includes a visual strength indicator when entering a new password. Very Weak, Weak, and Common passwords are blocked and aren’t allowed. However, a small bug existed that could allow a weak password to be chosen during a password reset. This has been resolved for v4.42.

Fixed: Not possible to add new user accounts in suspended state

Administrators have extensive control over the permissions that can be assigned to each individual user account. Individual user accounts can also be quickly ‘Suspended’ by an administrator. Until now, however, a small bug prevented new user accounts from being added in an initial ‘suspended’ state. This has now been resolved for v4.42.

3rd Party Deprecations and Updates

MIDAS includes a small number of 3rd party components, and it’s important to us that we use the latest versions of these wherever possible.

To that end, for MIDAS v4.42 we’ve updated jQuery to v4.00 and jQuery-Autocomplete to v1.5.0.

We’ve also deprecated qTip2, as this is no longer maintained by the developer. qTip2 was used in MIDAS for dynamic tooltips, like those you see when you ‘hover’ over the name of a venue in the booking grid.

Instead, we’ve built our own dynamic tooltip system from the ground up for v4.42.


Our Green Credentials

The impact that businesses have on the environment is a issue that’s close to many people’s hearts.

We’ve all see news stories of how we as consumers can make changes to reduce our carbon footprint. Many responsible businesses also take steps to monitor and reduce their carbon footprints too.

Here at MIDAS, we’re committed do the same!

MIDAS’ Carbon Footprint

We’re pleased to report that since 2021, we’ve reduced the carbon footprint of MIDAS by 5%.

Back in 2021, we first discovered the Website Carbon Calculator. This innovative website analyzes five key metrics to estimate the carbon emissions of any website. These factors include the volume of data being transferred when a web page is viewed, the type and amount of energy used at the data center serving the web page, as well as the volume of traffic to the site.

When we analyzed our website using the Carbon Calculator in 2021, it reported that MIDAS was cleaner than 86% of all web pages tested.

Now in 2025, we’re now greener than 91% of all web pages globally.

MIDAS is cleaner than 91% of all web pages globally
MIDAS is cleaner than 91% of all web pages globally

Reducing Carbon Dioxide Production

The Website Carbon Calculator further estimates that only 0.10g of Carbon Dioxide is generated when someone visits our website. This is down from 0.19g in 2021.

Only 0.1g of CO2 is produced per page on our website
Only 0.1g of CO2 is produced per page on our website

Backed by Green Sustainable Energy

Additionally, the Green Web Foundation provides a “Green Web Check” tool, which can provide an indication as to whether a web site (or service) is backed by green sustainable energy.

The Green Web Check affirms that our website/network (including our cloud hosted customer’s booking systems) is backed by green energy.

MIDAS runs on green sustainable energy
MIDAS runs on green sustainable energy

Choosing greener online businesses

MIDAS produces 60 times less carbon than some of our competitors

When focusing on reducing carbon footprints, many businesses look to do this in “visible” ways. One common approach is to replace tungsten bulbs with more efficient low energy LED light bulbs.

But how many consider the software their business uses when looking at ways to reduce their carbon footprint? It’s a less obvious and certainly a less “visible” action.

But when you consider that significant differences that do exist today between different software vendor’s carbon production, choosing a software vendor with a low carbon footprint makes sense! Not only does it help with your own business’ green credentials, but it also – more importantly – it helps our planet.

So for a room booking and resource scheduling system committed to being green, be sure to consider MIDAS.


Cloud Infrastructure Upgrades – December 2024

Cloud Infrastructure

Last week we undertook some upgrades in the three client data centers where our cloud-hosted customer’s MIDAS systems reside.

These data centers are located Atlanta, Georgia (US East Coast Data Center), Seattle, Washington (US West Coast Data Center), and Amsterdam, Netherlands (European Data Center).

When a customer chooses a cloud-hosted edition of MIDAS, they can choose which of these data centers their booking system runs from. (We also offer a self-hosted edition too, for customers wishing to run MIDAS on their own infrastructure)

The upgrades to the sever ‘nodes’ where our cloud-hosted client’s MIDAS systems run include:

  • Increased CPU cores by 50%
  • Increased Memory capacity by 50%
  • Increased port speed by 50%

These upgrades were performed seamlessly without any downtime or impact on customer’s MIDAS operations.

The result of these upgrades is that we can deliver more powerful client nodes, with improved network connections.

In turn, this translates to even more responsive MIDAS booking systems for our customers. It’s all part of the service and commitment we have to our end-users!