Timeline
Megam had three phases: the Megam Systems phase, the Rio/OS phase, and the October 2018 pivot. The dates below show how the project evolved over time.
Phase 1 - Megam, Jul 2012 to Jul 2017
Jul 2012 - Megam project starts
Megam began as a project to build cloud identity for enterprise, then became Megam Systems and pivoted toward code-to-cloud. The first project was https://github.com/megamsys/deccanplato. This record treats July 2012 as the project start and March 2013 as the company-registration period.
Mar 2013 - Megam Systems, Chennai
Megam Systems operated from Chennai, India. The public GitHub organization still identifies the organization as Megam Systems and points to docs.megam.io.
2014 - Megam's OpenNebula architecture became public
The OpenNebula material described Megam as a code-to-cloud system across private, public, and hybrid clouds. The 2014 deck credited Varadarajan Narayanan, Kishore Kumar Neelamegam, Thomas Alrin, and Raj Thilak, and listed Java, Play, Ruby on Rails, Node.js, and Akka as supported frameworks.
The same material included TOSCA, an OpenNebula Chef plugin, private cloud installation, and Cloud-in-a-Box. This is the earliest public architecture anchor for Megam.
2014 - Docker Global Hack Day #2
Docker's archived Global Hack Day #2 results listed Visual Docker by Thomas Alrin, Yeshwanth Kumar, and Rajthilak second by vote count among "Other projects receiving top votes", with 457 votes.
Dec 2014 - OpenNebulaConf Berlin
OpenNebulaConf 2014 ran in Berlin from Dec 2-4, 2014. Kishorekumar Neelamegam presented Megam Cloud Automation Platform there, and the talk remains one of the primary public artifacts for the early system.
2015 to 2017 - Vertice, Nilavu, and the hosting-provider phase
Megam's public docs described MegamVertice as a platform for virtual machines, apps, and containers. The docs named Nilavu as the console UI, the API gateway as the API layer, and Vertice as the omni scheduler.
The product targeted operators running infrastructure such as OpenNebula, OpenVZ, Docker, and Ceph, with WHMCS billing, storage, snapshots, logs, and custom application flows in the product vocabulary.
Megam had 11 named Phase 1 customer accounts: Alternative-Energies.fr, Astimp.ro, AtomDeploy.com, FlexVPC, INTERGRID, Jonathan Rack Servers, MilesWeb.com, QuadCloud, RioCorp, Simha Online, and TIC Servicios.
Phase 2 - Rio/OS, Jul 2017 to Oct 2018
2017 - Rio/OS begins
Rio/OS introduced a product surface around rioos, commandcenter, autorio, aran, beedi, and ottavada. Supporting repositories such as metgroup, nalperion_rust, and openio-sdk-rust are libraries, not the main product surface.
2017 to 2018 - Rio/OS engagements
Rio/OS had CogMob as an enterprise pilot and ServerNet as a pilot enterprise customer. Intergrid belonged to the Megam-era SMB pilot/customer story. DET.io was associated with Megam only: a Megam partner, not a customer and not a Rio/OS partner.
2018 - Rio Advancement
Megam Systems was acquired by Rio Advancement Inc., led by Paul Sanar. The acquisition came with a promise of seed funding to extend Rio/OS development, and that funding did not fully materialize.
Phase 3 - Pivot, Oct 2018 onward
Oct 2018 - Lendsmart / Getattune
Kishorekumar Neelamegam met AK Patel, founder of Lendsmart, through Paul Sanar at a product demo. In October 2018, the team relocated to Lendsmart / Getattune, and active Megam/Rio/OS product development ended.
Kishorekumar eventually became co-founder of Getattune. The closure event was a decision and a pivot, not a slow decay.
After 2018 - Open source remains
Megam and Rio/OS were fully open source and never really closed. The code remains publicly useful as an artifact of what was built, even where individual GitHub repositories have incomplete license metadata.
2026 - Closure site
The closure site brings the Megam and Rio/OS story back into view as a concise history of what was built, what shipped, who worked on it, and why the product line ended.