Is Frontastic SaaS, PaaS
(or perhaps IaaS)?

A question that has probably bothered many already. ;-)

And while 99% of the population does not know what SaaS (Software-as-a-Service) and PaaS (Platform-as-a-Service) or even IaaS (Infrastructure-as-a-Service) are, there are an estimated 0.01% of technology enthusiasts who are prepared to deepen a fundamental discussion here.

But for what? What is it?

In this article I try to explain the advantages of “as-a-Service” in a generally understandable way. A small Overview to “Everything as a Service (XaaS)” I had already created in my article “Frontend as a Service for Dummies“.

So if you are interested in understanding the difference between IaaS, PaaS and SaaS, or if you just want to know where Frontastic fits in here, you should read on.

“Everything-as-a-Service in a nutshell: It’s about responsibility.”

What exactly is the difference between IaaS, PaaS or SaaS?

As already indicated, it is ultimately a question of responsibility.

With classic on-premise software (i.e. purchased licences), the buyer is responsible for everything: from the hardware on which the software runs, through maintenance (i.e. regular updates), to operation (e.g. ensuring availability).

  1. Infrastructure-as-a-Service (IaaS) provides classic computing power or memory. IaaS goes one-step further than traditional hosting by abstracting more from the actual hardware. But the transition is smooth. Roughly, however, it can be said that the responsibility for the purchase and operation of hardware is given to the service supplier.
  2. Platform-as-a-Service goes another step further. Usually this service is based on an IaaS, but also provides an application environment. This is a software environment on the basis of which application programs can be created. Here, the responsibility for the operation of the software platform is handed over to the service supplier. In eCommerce, platforms such as Salesforce Commerce Cloud or About You Cloud should be mentioned here. They offer a basis on which concrete solutions can be built.
  3. Software-as-a-Service is characterised by the fact that it is usually a complete solution that only needs to be configured for the respective application. The responsibility is completely transferred to the service provider – apart from creating the content of course. This includes all eCommerce solutions that are offered more or less ready-made from the cloud.
    At this point, there is one small catch: SaaS offers from the so-called Private Cloud. This is usually classic on-premise software that is operated as a service in a virtual environment for a single customer.

The Private Cloud is a technological transition phenomenon, as is the hybrid drive in cars. This drags along the contaminated sites of the internal combustion engine and thus prevents the potential of the electric drive from being exhausted. The same applies to the private cloud: it can hardly benefit from the advantages of modern cloud offers. It is rather a Managed Service from the nineties with a new label.

On-premise, IaaS, PaaS or SaaS –
explained in simple terms

On-Premise, IaaS, PaaS and SaaS – explains from purchasing to tablecloths.

The responsibility for the pink fields lies with the consumer. Violet marks out-sourced responsibility.

As I said before, it helps understanding a lot to focus on who is responsible for what.

  1. With the good old On Premise Software you are responsible for everything yourself. One thinks of a process (recipe), buys accordingly the software (the ingredients), operates/waits (cooks) and delivers to the user (served), incl. support.
  2. With IaaS you buy the infrastructure. It’s like buying convenience food. You still have to prepare, but you don’t need to worry about the recipe and the right choice of ingredients.
  3. PaaS can be compared to a delivery service. Here the preparation is also taken care of. I’m still free to set the table festively but my kitchen stays cold. I can fully focus on my festive table and meal.
  4. For SaaS, it’s all about the festive meal. I find a nice restaurant and hand over the responsibility for all other processes to others.

Every company should consider where its core competence lies and from which processes it draws the greatest added value. This determines whether IaaS, PaaS or SaaS is the right choice.

But to rely on On Premise Software today would be equivalent to a strategic investment in diesel engines.

… and finally the resolution:

Frontastic is Frontend-as-a-Service

Frontend-as-a-Service is a combination of Software-as-a-Service and Platform-as-a-Service. Of course we use an Infrastructure-as-a-Service as the basis of our services. And of course we also use other software as a service to complete our services.


Agencies we offer a Platform (as-a-Service) on the basis of which you can develop customer-specific additions to our standard software.

Customers use our frontend as Software-as-a-Service. Together with the agency (or the in-house programmers) they can easily create a Mobile-First customer experience and concentrate fully on this experience.


What’s your opinion?


3 replies
  1. New York Global Consultants
    New York Global Consultants says:

    Certainly agree with just what you said. Your explanation was certainly the simplest to comprehend. I tell you, I usually get annoyed any time folks discuss issues that these people obviously dont know about. You were able to hit the nail on the head and spelled out the whole thing with out complication. Perhaps, folks could take a signal. Will likely be back to obtain more. Appreciate it

    Infrastructure as a Service (IaaS) Providers in Japan | IT Consulting Companies


Trackbacks & Pingbacks

  1. […] takes the lead in the API Economy and revolutionises the market. Frontastic’s cloud platform is designed to emotionalise […]

  2. […] takes the lead in the API Economy and revolutionizes the market. Frontastic’s cloud platform is designed to emotionalize […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *