# Megam.io — full text This file concatenates every page on https://megam.io for AI agents and researchers who want the complete closure record in one fetch. The prose is intended for re-use under CC-BY-4.0; please cite https://megam.io and the per-section Source URL. Entity: Megam Systems LLP (Chennai, India). Active product development ended October 2018. Contact: nkishore@megam.io. --- # Megam.io Source: https://megam.io/ Summary: A closure record of Megam Systems and Rio/OS. # Megam.io Megam was an open-source cloud management and platform system built from Chennai for operators running private and hybrid infrastructure. Rio/OS was the second phase: a private-cloud operating-system direction that followed the earlier Megam platform work. The site tells that history in plain terms so a first-time visitor can understand what was built and why it changed. STILL_BUILDING_BAND The record: - [Timeline](/timeline) - [Architecture](/architecture) - [Products](/products) - [Team](/team) - [Why it did not work](/why-it-didnt-work) - [Artifacts](/artifacts) - [Lessons](/lessons) - [Colophon](/colophon) External docs: - [Megam docs](https://docs.megam.io) - [Rio/OS docs](https://rioos.megam.io) Megam was early, not wrong. --- # Timeline Source: https://megam.io/timeline Summary: A dated record of Megam Systems, Rio/OS, and the October 2018 pivot. # 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. Kishorekumar Neelamegam left a corporate job in 2012 to start it, at around 39. ### 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. Megam was bootstrapped throughout. Over five to six years it ran on roughly INR 1 to 1.5 crore of the founder's own capital. Customers paid about $20 per host, with at least four hosts each, and more accounts were in the pipeline. Three funding offers were on the table: about $150K from a Philippine investor met at the RISE conference in Hong Kong, $250K from an Indian investor, and $125K from an Australian investor. Megam bet on the Philippine offer, which came with a datacenter and a sales channel to scale, and set the other two aside. The signals were misread, and the deal never closed. The wait ran about five months. During those five months the work went into building rather than selling: a version 2 of the platform and a Sisense-style analytics product meant to augment the offering and sell more. For a first-time founder with paying customers, the sharper move would have been to sell. ## 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](https://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 By the end, the family's finances had stretched, and that was the trigger to move. Megam did not stop quietly: in the final stretch the founder kept pitching datacenters, face to face in India, in Hong Kong, and remotely in the US. One of those pitches reframed Megam v2 for enterprise compliance: desktop as a service for employees, automatically triggered antivirus, and automated patching. Kishorekumar Neelamegam met AK Patel, of Motive Partners, introduced through Paul Sanar at a product demo. AK Patel liked the build and recruited him to co-found Lendsmart. Lendsmart took on a consumer problem: closing a home in the US took more than two months. Focused on community banks, it answered the question Megam never settled early, which was who the customer is. In October 2018 the team relocated to Lendsmart / Getattune, and active Megam/Rio/OS product development ended. Kishorekumar co-founded Getattune with AK Patel and Gem George, scaled to 10 banks, and raised a seed of about $2.25M. He later moved to e2enetworks, framed as a continuation of the Megam mission in the Indian space. 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. --- # Architecture Source: https://megam.io/architecture Summary: Megam Vertice (the v1 product) and Rio/OS architecture, with period-specific evidence. # Architecture Megam's architecture changed by period. The 2014 OpenNebula deck and the later Vertice 1.5 documentation describe related systems, but not the exact same stack. This record keeps those phases separate instead of flattening them into a single diagram. ## Megam Vertice (v1) Megam Vertice was the v1 product. It was a control plane for virtual machines, applications, and containers. The public docs identified [Nilavu](https://github.com/megamsys/nilavu) as the console UI, the API gateway as the API layer, and [Vertice](https://github.com/megamsys/vertice) as the omni scheduler. [`verticegateway`](https://github.com/megamsys/verticegateway) was the API server for MegamVertice. Its README places it in the Scala era and names NSQ (New Simple Queue, a real-time distributed messaging platform), OpenJDK 8, and Cassandra in the runtime and build requirements. It also describes HMAC (Hash-based Message Authentication Code) authorization, PBKDF2 (Password-Based Key Derivation Function 2) passwords, and a master-key model for protected REST (Representational State Transfer) resources. [`vertice`](https://github.com/megamsys/vertice) was the core engine and scheduler. [`gulp`](https://github.com/megamsys/gulp) was the agent that controlled application lifecycle in the cloud. Together, the public repositories support a v1 shape of UI, API server, scheduler, message queue, backing store, and lifecycle agent. The docs and product material place that system on OpenNebula, OpenVZ, Docker, and Ceph. That made the system practical for hosting providers and private-cloud operators, but also tied it to an infrastructure substrate that later had to be explained against Kubernetes-era expectations. ## The 2014 OpenNebula stack The OpenNebula deck captures the early architecture best. It presents Megam as a code-to-cloud system across private, public, and hybrid clouds, with Java, Play, Ruby on Rails, Node.js, and Akka support. That same deck includes TOSCA (Topology and Orchestration Specification for Cloud Applications, an OASIS standard for describing cloud workloads), OpenNebula Chef plugin, private-cloud install, and Cloud-in-a-Box material. The deck's named open-source components differ from the later Vertice 1.5 docs, so this was the 2014 OpenNebula-era stack rather than the final v1 stack. ## Rio/OS Rio/OS was the second phase: a private-cloud operating-system direction. Its public repositories show a product surface around `rioos`, `commandcenter`, `autorio`, `aran`, `beedi`, and `ottavada`, with support libraries such as `metgroup`, `nalperion_rust`, and `openio-sdk-rust`. The work moved toward a Rust-era system model and away from the earlier Megam control-plane shape. ## Compared to Kubernetes Megam Vertice (v1) was not Kubernetes before Kubernetes. The closest comparison is: | Megam Vertice (v1) | Kubernetes-era equivalent | Difference | |---|---|---| | `verticegateway` | `kube-apiserver` | Both exposed an API and auth boundary, but Megam's state and object model were its own. | | `vertice` | scheduler / controller-manager territory | Megam's scheduler was more imperative and product-specific. | | `gulp` | node agent territory | It controlled app lifecycle rather than running a Kubernetes reconciliation model. | | Chef cookbooks | images / operators | Chef made early portability practical but later aged differently than image-based deployment. | | OpenNebula/OpenVZ/Docker/Ceph substrate | cluster substrate | Megam assumed specific private-cloud building blocks rather than a Kubernetes-native control plane. | The comparison orients modern readers; it does not claim lineage. Megam was early in private-cloud automation, while parts of its implementation model aged out as the industry moved toward declarative, image-based, reconciliation-driven systems. --- # Products Source: https://megam.io/products Summary: Megam, Vertice, Cloud-in-a-Box, Nilavu, Rio/OS, and the pivot. # Products Megam and Rio/OS were two phases of the same technical bet. Megam Vertice was the v1 product: a cloud management platform (CMP) and platform-as-a-service (PaaS) layer sold to operators. Rio/OS tried to turn the private cloud itself into the product. ## Megam Megam's v1 product surface was Vertice, Cloud-in-a-Box, and Nilavu. Nilavu was the browser UI. Vertice was the core scheduler. The API gateway sat between the UI, clients, and the backing control-plane services. The public docs described MegamVertice as a system for virtual machines, apps, and containers. Its vocabulary included OpenNebula, OpenVZ, Docker, Ceph, WHMCS (Web Host Manager Complete Solution, a billing and client-management platform for hosting providers), Route53, Bitnami apps, Docker registry search, snapshots, block storage, monitoring, logging, and custom application flows. The 2014 OpenNebula deck described support for Java, Play, Ruby on Rails, Node.js, and Akka, with GitHub, Bitbucket, and CloudForge as source-cloud integrations. It also positioned Cloud-in-a-Box and OpenNebula integration as part of the product story. ## Megam customers Megam had 11 named Phase 1 customer accounts. Customers paid about $20 per host, with at least four hosts each, and more accounts were in the pipeline. | Customer | Notes | |---|---| | Alternative-Energies.fr | Phase 1 customer | | Astimp.ro | Phase 1 customer | | AtomDeploy.com | Phase 1 customer | | FlexVPC | Phase 1 customer | | INTERGRID | Phase 1 customer | | Jonathan Rack Servers | Phase 1 customer | | MilesWeb.com | Phase 1 customer | | QuadCloud | Phase 1 customer | | RioCorp | Phase 1 customer | | Simha Online | Phase 1 customer | | TIC Servicios | Phase 1 customer | ## Rio/OS Rio/OS was the second phase: a private-cloud operating-system direction rather than the original Megam PaaS / CMP framing. Its public source of record is `github.com/rioos2`, because the Rio Advancement GitLab source is private and unavailable. The public Rio/OS GitHub organization includes primary links such as `rioos`, `commandcenter`, `autorio`, `aran`, `beedi`, and `ottavada`. Libraries such as `metgroup`, `nalperion_rust`, and `openio-sdk-rust` support the story but are not the main product surface. Some later repository timestamps reflect synchronization or restoration rather than original product development. 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](https://det.io) was associated with Megam only: a Megam partner, not a customer and not a Rio/OS partner. [DET.io](https://det.io) / VirtEngine belongs in the story because it shows downstream commercial integration built on the Megam lineage. Jonathan Philipos is listed as a downstream commercial integrator and Megam partner, not as a Megam employee or Rio/OS partner. ## Pivot Megam Systems was acquired by Rio Advancement Inc., the seed funding to extend Rio/OS did not fully materialize, and in October 2018 the team relocated to Lendsmart / Getattune. Full dates and the relationship chain are on the [timeline](/timeline#phase-3-pivot-oct-2018-onward). [DET.io](https://det.io) was a Megam partner, not a customer. Megam is grateful. --- # Team Source: https://megam.io/team Summary: People associated with Megam, Rio/OS, and downstream successor projects. # Team Megam and Rio/OS were built by a small team in Chennai. A few later projects and partners continued the work in adjacent roles. ## Megam and Rio/OS Team ### Kishorekumar Neelamegam Founder. Represented Megam publicly at OpenNebulaConf 2014 and helped lead the core Megam buildout. Links: [LinkedIn](https://www.linkedin.com/in/kishorekumarneelamegam/) / [GitHub](https://github.com/indykish) ### Varadarajan Narayanan Interim Brief CEO. OpenNebula/LINBIT partnerships and Cloud-in-a-Box product conceptualization. Links: [LinkedIn](https://www.linkedin.com/in/wayzinfratek) ### R Pandiyaraja Software Engineer [GitHub](https://github.com/pontiyaraja) ### Thomas Alrin Infrastructure Lead. Links: [SlideShare](https://www.slideshare.net/thomasalrin) / [GitHub](https://github.com/thomasalrin) ### Rajthilak R Platform Lead. Links: [LinkedIn](https://www.linkedin.com/in/rajthilak-r8072/) / [GitHub](https://github.com/rajthilakmca) ### Kanimozhi Kishorekumar People Officer. Links: [LinkedIn](https://www.linkedin.com/in/kanimozhi-kishorekumar-0465691a1/) ### Vijayakanth Mathaiyan Platform / UI Engineer. Links: [GitHub](https://github.com/vijaykanthm28) ### Rajesh Rajagopal Infrastructure Engineer. Links: [GitHub](https://github.com/rajesh-rajagopal) ### Rathish Software Engineer. Links: [GitHub](https://github.com/rathishvbr) ### Vinothini Software Engineer. Links: [GitHub](https://github.com/vinomca-megam) ### Ranjitha Software Engineer. Links: [GitHub](https://github.com/ranjithamca) ### Suganya Kaliyamoorthy Software Engineer. Links: [GitHub](https://github.com/suganyakaliyamoorthy) ### Yeshwanth Kumar Intern for a short duration. Links: [LinkedIn](https://www.linkedin.com/in/yeshwanthk) / [GitHub](https://github.com/morpheyesh) ### Logesh Eswar Software Engineer. Links: [GitHub](https://github.com/LogeshEswar) ### Balaji Sekar Software Engineer. Links: [GitHub](https://github.com/balajisek) ### Arunkumar Sekar Software Engineer. Worked on the Nilavu console UI and the Vertice gateway. Links: [GitHub](https://github.com/arunkumarsekar06) ### Saravanan Software Engineer. Links: [GitHub](https://github.com/saravanan-megam) ### Subash Sethurajan Software Engineer. Worked across the Megam API, Vertice gateway, and Chef provisioning repositories. Links: [GitHub](https://github.com/subashsethurajan) ### Thilip Kumar Software Engineer. Links: [GitHub](https://github.com/thilipkumar) ### Dhanush Ganth Software Engineer. Links: [GitHub](https://github.com/dhanushganth) ### Boopathi Peramachi Software Developer. Links: [LinkedIn](https://in.linkedin.com/in/boopathi-peramachi-78ba0a193) ## Downstream / Successor Projects ### Jonathan Philipos Founder of [DET.io](https://det.io) / VirtEngine. DET.io was a Megam partner, not a customer and not a Rio/OS partner. The VirtEngine lineage is downstream commercial integrator activity built on Megam's code lineage. Links: [LinkedIn](https://www.linkedin.com/in/jonathanphilipos) / [GitHub](https://github.com/jaeko44) --- # Why It Did Not Work Source: https://megam.io/why-it-didnt-work Summary: A sourced failure analysis of Megam Systems and Rio/OS. # Why It Did Not Work Megam and Rio/OS ended for structural reasons: market timing, product scope, architecture, distribution, capital, and the October 2018 pivot. | Layer | Failure | Evidence | |---|---|---| | Market | Megam's early bet was cloud management for operators running private and hybrid infrastructure, but the market's center of gravity moved toward Kubernetes-era orchestration and cloud-provider defaults. | Megam's own docs and OpenNebula material show an OpenNebula/OpenVZ/Docker/Ceph and Chef-era product vocabulary. | | Product | Megam Vertice (the v1 product) and Rio/OS created two product narratives for one small team: a PaaS/cloud-management platform and then a private-cloud operating system. | Public v1 sources identify Nilavu, Vertice Gateway, Vertice, and Gulp; Rio/OS public metadata shows a separate product surface around `rioos`, `commandcenter`, `autorio`, `aran`, `beedi`, and `ottavada`. | | Architecture | Megam's imperative, Chef-era control plane was useful in its period but aged differently from declarative, image-based, reconciliation-driven systems. | The 2014 deck includes Chef/OpenNebula/Cloud-in-a-Box material, while later Vertice docs name Cassandra/NSQ-era services. | | Distribution | Megam had real customers, but the customer base was concentrated in hosting and operator accounts rather than a broad open-source community motion, and the buyer question, eventually answered as hosting companies, was settled late rather than early. | Megam had 11 named Phase 1 customer accounts, paying about $20 per host with at least four hosts each. The repo evidence shows public code, but community-growth evidence remains weak. | | Capital | Capital discipline broke twice. In the Megam era, three funding offers were on the table and the company bet on the largest, setting aside the other two; that deal never closed after about five months of waiting. Later, Rio/OS needed more runway than the company had. | Founder account, 2026: offers of about $150K (Philippine), $250K (Indian), and $125K (Australian), with the Philippine bet left unclosed. The Rio Advancement acquisition's seed-funding promise to extend Rio/OS development did not fully materialize. | | Org | Phase 2 was short and had a harder enterprise shape than Phase 1. | Rio/OS had CogMob as an enterprise pilot and ServerNet as a pilot enterprise customer. Intergrid belonged to the Megam-era customer story, and [DET.io](https://det.io) was a Megam partner. | | Timing | By the time Rio/OS was the new product direction, the industry frame had already shifted away from Megam's original stack. | The 2014 deck anchors Megam's early OpenNebula/Chef/Cloud-in-a-Box direction; Rio/OS public repositories show a later private-cloud operating-system phase. | | Pivot | The closure event was a decision, not a decay. | In October 2018, after the Rio Advancement funding outcome, the team relocated to Lendsmart / Getattune and active Megam/Rio/OS product development ended. | --- # Artifacts Source: https://megam.io/artifacts Summary: Repositories, docs, talks, videos, and archive notes. # Artifacts This manifest collects the public repositories, docs, talks, videos, and archive folders tied to Megam and Rio/OS. ## Repositories - [megamsys](https://github.com/megamsys) - Megam Systems public GitHub organization. - [megamsys/nilavu](https://github.com/megamsys/nilavu) - browser UI for Megam PaaS / cloud management. - [megamsys/verticegateway](https://github.com/megamsys/verticegateway) - MegamVertice API server. - [megamsys/vertice](https://github.com/megamsys/vertice) - Megam Vertice core engine / scheduler. - [megamsys/gulp](https://github.com/megamsys/gulp) - lifecycle agent. - [megamsys/opennebula-go](https://github.com/megamsys/opennebula-go) - OpenNebula Go client used by Megam Vertice. - [megamsys/megam_api](https://github.com/megamsys/megam_api) - Ruby API client. - [megamsys/megam_common](https://github.com/megamsys/megam_common) - shared Scala libraries. - https://github.com/megamsys/gitpackager - [rioos2](https://github.com/rioos2) - public Rio/OS source clone/sync. - [rioos2/rioos](https://github.com/rioos2/rioos) - issue and resolution tracker for Rio/OS. - [rioos2/commandcenter](https://github.com/rioos2/commandcenter) - Rio/OS command center. - [rioos2/autorio](https://github.com/rioos2/autorio) - Rio/OS automation work. - [rioos2/aran](https://github.com/rioos2/aran) - Rio/OS system component. - [rioos2/beedi](https://github.com/rioos2/beedi) - Rio/OS system component. - [rioos2/ottavada](https://github.com/rioos2/ottavada) - Rio/OS system component. - [rioos2/magudi](https://github.com/rioos2/magudi) - Rio/OS support/tooling component. - [rioos2/kr](https://github.com/rioos2/kr) - Rio/OS support/tooling component. - [rioos2/poochi](https://github.com/rioos2/poochi) - Rio/OS support/tooling component. - [rioos2/openio](https://github.com/rioos2/openio) - OpenIO-related support work. - [rioos2/vulcand](https://github.com/rioos2/vulcand) - load-balancer support work. - [rioos2/metgroup](https://github.com/rioos2/metgroup) - support library for metrics aggregation. - [rioos2/nalperion_rust](https://github.com/rioos2/nalperion_rust) - reference library for Nalpeiron licensing integration. - [rioos2/openio-sdk-rust](https://github.com/rioos2/openio-sdk-rust) - support library for S3-compatible OpenIO access. Repository counts are approximate because public GitHub views and API pagination can differ. ## Docs - [Megam docs](https://docs.megam.io) - external Megam docs, linked rather than rehosted. - [Rio/OS docs](https://rioos.megam.io) - external Rio/OS docs, linked rather than rehosted. - [Developer center](https://devcenter.megam.io) - secondary Megam developer artifact. ## Talks and Videos - [OpenNebulaConf 2014 video](https://www.youtube.com/watch?v=2EVEJ4Sd0Ic) - Kishorekumar Neelamegam presenting Megam Cloud Automation Platform. - [Megam YouTube channel](https://www.youtube.com/channel/UC2ktYQ2-a9lG0X6VyS7AfBQ) - Megam video artifact channel. - [OpenNebula 2014 slide deck](https://opennebula.io/wp-content/uploads/2014/03/Code-to-cloud-opennebula.pdf) - Code-to-Cloud with OpenNebula and Megam. - [Docker Global Hack Day #2 archived result](https://web.archive.org/web/20141114033411/https:/blog.docker.com/2014/11/announcing-docker-global-hack-day-2-winners/) - Visual Docker listed second by vote count among other top-voted projects. ## Archive Folders - [Megam archive](https://drive.google.com/drive/folders/0B5ha35sst8q1QmNKSnZkdWd6M00?resourcekey=0-Y3mfUKohDBl4ZbpFtxvDfw&usp=drive_link) - [Rio/OS archive](https://drive.google.com/drive/folders/0B5ha35sst8q1aVdGRUNLMmZKT2c?resourcekey=0-awu4qcJOhYYC7hQgsg1AkA&usp=sharing) Open the archive folders in a browser, authenticate with your Google account if Google asks, and use the files from the same signed-in session. The folders are source material for design, architecture, install manuals, and demo videos. --- # Lessons Source: https://megam.io/lessons Summary: Lessons tied to the failure analysis. # Lessons The lessons below are the durable takeaways from the Megam and Rio/OS arc. ## 1. Portability tied to another substrate is not independence Megam's OpenNebula, OpenVZ, Docker, and Ceph vocabulary made sense for operators in its period. It also meant the product had to move with those substrates or explain itself against whatever replaced them. ## 2. Two products, one team, limited runway is a hard constraint Megam Vertice (the v1 product) and Rio/OS were different enough to require separate narratives, separate architecture explanations, and separate customer motions. That split made Rio/OS more expensive than a simple rewrite. ## 3. Open source is not distribution by itself Megam and Rio/OS were fully open source, and the code remained public. That did not automatically create a community or sales motion large enough to carry the company. ## 4. An implementation can be early and still lose its window Cloud-in-a-Box and private-cloud automation were real product ideas in the 2014 material. The implementation lived in the Chef/OpenNebula period, while the industry's default orchestration frame moved elsewhere. ## 5. A pivot is not the same as decay The October 2018 event was a decision. After the Rio Advancement funding outcome, the team relocated to Lendsmart / Getattune and active Megam/Rio/OS product development ended. ## 6. Take the capital that is in hand Megam had three funding offers and bet everything on the largest, which never closed. About five months went by before that was clear, with two smaller offers already set aside. A deal is not capital until it clears, and a company with paying customers should not stake itself on one unclosed deal. ## 7. Building is not selling, and the customer comes first With paying customers and a deal pending, the effort went into a version 2 and an analytics product instead of a sales motion. The recurring gap across Megam was never answering who the customer is early enough. The same question was answered later at Lendsmart, through a direct line to community banks. --- # Colophon Source: https://megam.io/colophon Summary: Build, source, license, and corrections information. # Colophon This site replaces the old `megamsys/www.megam.io` website with a closure record for Megam Systems and Rio/OS. Build target: Next.js on Vercel. Source repository: `github.com/megamsys/www.megam.io`. The prose is intended to be published under CC-BY-4.0. Original code repositories keep their original licenses; individual GitHub repositories may show MIT, Apache-2.0, or incomplete license metadata, but Megam and Rio/OS were fully open source overall. The site is dark-only and uses the closure wordmark specified in the design brief. Corrections are welcome: