Why implement a hybrid-cloud or cloud-tethered solution?

Sabisu is unusual in that it was designed from the very beginning as both a cloud and on-premise solution. Sabisu’s hybrid-cloud and cloud-tethered architecture delivers new capabilities ahead of customer demand so that customers can realise competitive advantage.

Designing the platform in 2010, the team was fortunate that cloud technology was sufficiently mature and the likes of Facebook and Google had demonstrated some compelling value propositions, engineering and business models.


So why take on the cloud? And why keep the on-premise? What’s the difference between hybrid and cloud-tethered? And how does it work?

Why cloud?

  • Supports a zero-IT SaaS rollout in a matter of hours, disrupting traditional enterprise IT models
  • Direct channel for communicating data to vendors, partners and 3rd parties, delivering an ‘extended enterprise’ capability
  • Infrastructure to support exploration and development future value propositions
  • Central point to support a distributed architecture for globally distributed enterprises
  • Supports deployment of data to enterprise users outside the enterprise network, e.g., on mobile devices.
  • Ensures all customers continually benefit from the Sabisu agile devops approach
  • Elastic compute resource to support rapid expansion and onboarding new customer

The cloud really works for us and has proven key to all those points.

So an SaaS deployment is entirely possible. In fact, it’s key to Sabisu, as it’s often the initial engagement with a new customer.

Architecture v2 - SaaS

Why keep the on-premise?

If the cloud is so great, why not offer Sabisu as a purely SaaS play?

Simply put, that’s not what the customer needs. Most of our customers have vast quantities of enterprise and manufacturing data in the enterprise and do not want to risk that data, either by shifting it to the cloud or by exposing it to our cloud via something like VPN.

All enterprise data is served directly from the on-premise within the enterprise network to a client. We guarantee enterprise network integrity.

Architecture v2 - Hybrid

The on-premise looks after authentication, integration and aggregation. It sits within the customer’s network so they can be confident that their data isn’t leaving their enterprise unless they specifically instruct that it should. Even then, only aggregated data is passed.

The on-premise is close to the source data so that aggregation, calculations and analytics can be fast. Sabisu doesn’t have to move large quantities of data to the cloud.

The on-premise is designed for deployment anywhere; middle of an enterprise network, edge of a distributed network with limited bandwidth, in the cloud to demarcate separate projects or organisations.

On-premise servers also have a trick up their sleeves; they can be federated to allow load balancing or inter-premise data exchange.

Architecture v2 - Distributed

Hybrid-cloud + Cloud-tethering = hybrid-SaaS

The cloud is a self-provisioning, resource pooled, possibly multi-tenant, elastic compute resource. So a hybrid-cloud is a combination of this with an on-premise component.

If the cloud’s elastic compute capability is needed it’s easy to utilise; spin up another server to scale, scale using services, aggregate a little less on-premise or load the bandwidth to the cloud a little more.

All that great cloud capability mentioned at the top of this post is in play, but with the added capabilities of the on-premise, particularly around integration.

The on-premise component could be highly virtualised itself – a virtual, private cloud, consisting of hundreds of on-premise servers. Or it could be a lone server. It doesn’t matter to the end user.

The on-premise and cloud is brought together seamlessly on the end-user’s machine. Therefore it would be more useful to call Sabisu a hybrid-SaaS platform; to the user there is no discernible gap between the cloud and on-premise experience.

Of course, some key capabilities such as external access, collaboration and distribution of data depend on that cloud capability as it acts as the conduit, effectively tethering the user to the cloud and on-premise servers to get the full range of Sabisu capabilities.

This gives the ability to implement new capabilities at zero cost, e.g., pushing data to plant mobile devices without any changes to IT infrastructure to gain substantial bottom line efficiency savings.

And that’s where tethering comes in; ensuring that users have on-demand access to product features as soon as they’re available so they can get that competitive edge.


Start typing and press Enter to search