easy private
computing cloud

simply virtualize your infrastructure
and keep your data safe



Try it!

Try CoreCluster at our online demo installation, available here


Cooperation with the Ministry of Foreign Affairs

Nov. 10, 2018, 9 a.m.

Cloudover has started cooperation with the Ministry of Foreign Affairs of the Republic of Poland. Together with other Polish companies, we have pleasure to participate in the Polish Technology Hub, which connects multiple IT companies focused on the development of innovative technologies.


Moving to Gitlab

Nov. 2, 2018, noon

As you might noticed last time Cloudover's activity at our Github account has been decreased. Reason of that is that couple months ago we've moved to our internal Gitlab.

Such movement allowed us to better integrate development, testing and migration to Python3 (which will probably take couple months more). Soon gitlab service with CoreCluster and all dependencies should be available to public.

Meanwhile there is large progress in dinemic project, which aims to replace existing CoreCluster architecture with new, blockchain based one. This will move CoreCluster again, in the same direction as now - to create yet more simple project wit hbetter functionality and security

If you need access to source code repositories, please let us know. It should be available for public till end of this year.

Libdinemic is AGPL

May 21, 2018, 11 a.m.

Recently source code of libdinemic framework was published as AGPL on Github.

Meanwhile, the main goals of library were published in Applied Computer Science paper. The article is open access, so you can read how libdinemic works and how it handles applications written with this framework. In future, libdinemic aims to be base for CoreCluster cloud and become fully decentralized virtualization and cloud engine, including software defined networking and storage.

CoreCluster demo

May 21, 2018, 10 a.m.

CoreCluster demo installation is available again

To check, visit demo.cloudover.io and create new account. You can create new virtual machines, manage network and check basic functionality of CoreCluster cloud.

CoreCluster 17.11 is out

Nov. 3, 2017, 1:53 p.m.

CoreCluster is now in new stable version.

  • Installation for Debian 9 Stretch, with all requirements is now supported
  • Fixed HTTP headers for Same Origin Policy in new web browsers
  • Fixed hook subsystem and some important CoreCluster's hooks
  • Support for Coremetric and Coremetry modules
  • New algorithm for node selections. Old default is now called fillup (tries to fit most filled nodes first). The new one is median - fills nodes with median CPU usage first. This should prevent using all nodes at once, without cumulating all instances at one node at time.
  • Fixed some minor bugs (model edit, corosync, api.image.create function, node shutdown and coretalk module)
To upgrade your system, do as usual: backup your data and databases, upgrade packages, migrate database, restart corecluster service and then uwsgi and services. To upgrade nodes upgrade packages and restart corenode service.

Libdinemic stable version

Oct. 23, 2017, 9:52 p.m.

Libdinemic is now in first, stable version: 0.1.1. Still needs a lot improvements, but key features are working:

  • Simple application skeleton - a very simple base class for all applications - no need to hours of learning API. Just inherit and code!
  • Event Driven Applications - you only create models, update data and monitor changes in database with dynamic actions. No need to create additional APIs to communicate across cluster - everything is driven by libdinemic.
  • Application autodiscovery - no network configuration needed for your applications. All cluster's applications will find each other automatically!
  • Authentication based on cryptography - no central point. Once application writes its data to the cluster, it is spread across whole cluster, signed by cryptographic API. Anybody in cluster could verify all other participants
  • You decide to who you trust, by filtering data updates - want to listen for everybody - ok! Want to filter unauthorized updates - just use predefined listeners

In principle, libdinemic is an wrapper for data stores, based on key-value databases. It allows to simply map C++ classes onto data structures in database. The library's architecture is designed to be a proxy to database, which shares all updates across network.

Applications using libdinemic could define own actions (DAction classes) and map them as listeners for updates of database, made by other nodes in cluster. This is the simplest way to connect ORM, database and API in one library. With underlying cryptography, it allows to verify all changes in database in secure way, giving to the developers powerful tool for creating distributed applications.

Find more

If you are interested, follow or star our repository at Github. You will find more in docs/ directory of this repo.

Compilation and installation

To compile and install follow instructions at our github repository: github.com/cloudover/libdinemic/.

Docker Workshops

Oct. 23, 2017, 9:49 p.m.

At upcoming Wednesday we have pleasure to invite you to the next KrakCloud workshops - Docker basics.

Grodzka 42/1, at Cluster Cowork in Krakow. Bring your laptop - everything else is right at the place. Register at KrakCloud Meetup

Libneon becomes libdinemic

Sept. 19, 2017, 7:10 a.m.

Since early 2017 cloudover.io develops the decentralized framework for distributed clusters of applications, based on cryptography. Orginally it was named libneon. Since September libneon becomes libdinemic.

Libdinemic is a framework, which hides difficulties related to accessing underlying database, monitoring changes in data and sharing those changes with other nodes in network, in secure way. Each update of data, done with Libdinemic framework is digitally signed and joined into chain of updates. Every node in cluster could verify each update, to make sure that nobody has tampered the data. Security in such ecosystem is delivered on the ORM Object level, and allows to easily manage permissions on particular objects, without any centralized authority. Libdinemic enforces using the Event Driven application model, so it becomes both: database API and communication channel for your applications.

In September this library was released in beta version. Libdinemic allows to use basic ORM on underlying database (at this time only Redis) and define own actions to be triggered on events in database. However, main improvement is fully functional autodiscovery of database nodes and sharing database changes across whole cluster, even for partially connected nodes.

For details, check project's website: lib.dinemic.io

CoreCluster 17.06

June 18, 2017, 8:40 p.m.

Next release of CoreCluster is out! Check for changes

  • Refactored command line tool - cc-manage. Each extension could define its own subcommands for cc-manage to provide additional functionality.
  • Fixed bug with priviledges handling in groups
  • Updated mechanism for counting API statistics
and some more minor bugfixes. During update a database migration is required. Before upgrading, backup your data.

Neon gets the MIT licensing

May 30, 2017, 4:15 p.m.

The Neon library, which will be new base of CoreCluster is now shared under MIT license. It is still in experimental phase, however you can find now some of its parts are ready for tests.

Since end of 2017 cloudover.io develops new base for CoreCluster cloud. Main idea is to change existing, centralized architecture with management node with single database to distributed system, based on blockchain, P2P and X509.

Neon is the library joining main concepts of ORM, Event Driven Development, distributed computing and cryptography. In very nutshell you can also call it a semi-blockchain protocol with additions. Stable version of Neon will guarantee data synchronization across whole cluster, without centralized server.

Each node in cluster will handle its own, most actual copy of database. All updates, changes and modifications of any objects in database are authorized by cryptographic tools, provided by GPG and OpenSSL libraries. So, as far as there is no central point, there is still very strong accent on security. Only node owning the database object's private key can update its state.

Moreover, Neon API grants some mechanisms to manage this privileges, by authorizing new keys to objects. All this features are based on well-known libraries.

Neon is written in C++, so its main API is available now only for this language. However additional language bindings will be available soon.