Why MAMAS?

There are a lot of various, general-purpose RMM solutions out there, so where does MAMAS stand out? How does a new product dare to compare to mature and existing solutions? Why should anybody (and who) consider using it?

When building a software as a new product or service to a busy market, there are a few possible strategies. One is to build an all-purpose full blown tool from the beginning and another one is to focus on a particular segment, thus narrowing required featureset.

The initial versions of MAMAS (until MAMAS 1.0) are targeted on a specific segment but with easy extensibility in mind. A few other key points are reflected in the product as well right from the beginning - usability and performance.

MAMAS 0.6-0.9 targets RMM functions for cellular routers, in the very first minor versions focusing on the Advantech brand. As for the easy extensibility, any devices running Linux OS can be added directly using the generic Linux agent which covers the basic Monitoring and Alerting functionlities. The generic client runs on most of supported distributions and also on FreeBSD and similar UN*X-like OSes.

Architecture-wise, the server requires x86-64 architecture (if deployed on customer server, that is) but clients can run on any OS that provides bash and curl.

The initial featureset is built with the system admin mindset to cover the most commonly needed use-cases for the target segment. That's something that the Dwarf Technologies company possess as the authors have deep technical knowledge across server administration, development, service operation, architecture, product management and integration of the whole change of thousands details that brings together a successful product or service.

First version shown to a selected audience was MAMAS 0.6 called early1 and next to the announced monitoring and alerting, it offered basic management functions for router's firmware management, remote web access and also automation in the form of configuration cloning. The product comes with intuitive interface and also documentation - both online and in-app help that comes in handy when deployed on private network and supporting howto videos.

We quickly followed with version 0.7 (early 2) bringing overview of software packages on routers, Data Change Log showing the actual history values with customizable view, improved overview of devices states, improvements in alert management and evaluation and finally, improved performance and a ton of smaller improvements.

During the 0.7.x line we are continuing adding smaller improvements like showing signal strength, improving the Changes Tracker and, most notably, adding mass actions like mass firmware flash allowing to apply the operation to a large set of devices in one go.

As the MAMAS is gaining customers, we are keeping with all the requirements flowing in, focusing our prioritization on keeping our current customers satisfied and incrementally enriching the featureset.

There are however a few aspects we are dedicated to right from the beginning, like:

• usability - our product needs to be usable, providing the users lightning fast overview of the devices and their state, a quick way to determining the problematic points and advices how to deal with these. We are focused on usability and continually improving.
• security - a lot of companies require to run their fleets in private network, completely isolated from Internet. A lot of RMM tools are lacking in this area but we ade dedicated to offer the same features on-premise and on the Internet. Also, the way MAMAS is built allows to have a dedicated installation for every customer thus not combining multiple customers data in under one application - something which is unfortunately common when using a lot of cloud solutions.
• performance - we are hard pressing ourselves to offer leading performance software. We optimize what is needed the most and carefully design and code the performance-critical areas. As a result, MAMAS is able to operate tens of thousands of devices even if you deploy the server on a notebook, on a small VM or an industrial PC. We also do publish results of performance and stability testing for every minor release.
• professional approach - we do communicate our release status, known issues and publish documentation and howtos both on the Internet and also in-app so that the users can access the most relevant and actual information in every scenario.

It is always hard to compare two products. You can write down a table with checkboxes to see what is supported by each of the compared software, but this will not tell you HOW does the products support your needs. It also does not tell you anything about the quality, performance and support you will be getting. But don't be mistaken - we do not discourage you from making your own comparison. We are quite sure that even in the version 0.7 our product does tick a lot of checkboxes - especially if you are after the initial market we are aiming at the beginning - cellular routers management.

No, let's go for it. Do your comparison. Or we can offer something better - a demo. If you are considering using MAMAS, let's request a demo. Let's look at what's there. Let's look at what is missing and tell us. Reviewing the pace we are growing product features and the dedication we answer our customer's requirements together with our care of providing accurate information and helping material and then consider if it is the right product for you. And if not? Well, lets revisit after some time as we are building the product rapidly and 0.7 is still far from 1.0!