MayaData

MayaData
Name	MayaData
Type	Private
Industry	Cloud computing, Data storage, Software
Founded	2013
Headquarters	Santa Clara, California, United States
Key people	Murali Basava, Kannan Muthukkaruppan
Products	OpenEBS, Mayastor, DataOps solutions

MayaData is a software company focused on cloud-native storage and data orchestration for containerized environments. The firm develops open source and commercial offerings aimed at persistent storage for Kubernetes, enabling stateful workloads across hybrid and multi-cloud deployments. Its work intersects with projects and organizations in the cloud-native ecosystem, including storage, orchestration, and data management initiatives.

History

Founded in 2013, the company emerged during a period of rapid growth for containerization led by projects such as Docker (software) and orchestration platforms like Kubernetes. Early development aligned with trends set by contributors to Cloud Native Computing Foundation projects and by vendors supporting OpenStack and cloud-native storage. Leadership included engineers with backgrounds at firms active in storage and virtualization, and the company expanded through developer engagement with upstream communities including maintainers of projects such as Prometheus (software), etcd, and other infrastructure components. Over time the organization shifted focus from general virtualization tooling toward specialized persistent storage for containers, contributing to and commercializing technologies that integrate with ecosystems maintained by entities like Linux Foundation and distributions from vendors such as Red Hat.

Products and Technology

Product offerings center on container-attached storage and data orchestration. The flagship open source project provides a containerized storage engine that exposes block and file interfaces to orchestrators like Kubernetes while leveraging storage primitives from underlying platforms, including features inspired by systems such as Ceph and ZFS. Complementary components address backup and recovery patterns similar to those implemented by tools like Velero (software), snapshot management reminiscent of LVM (Linux) and replication strategies found in enterprise arrays from vendors such as NetApp and Dell EMC. The stack implements data locality, caching, and thin provisioning strategies comparable to approaches used by GlusterFS and distributed storage systems employed by hyperscalers like Google and Amazon Web Services for block storage services.

Architecture and Integration

Architecturally, the platform integrates with Kubernetes control planes and uses container storage interface models similar to standards promoted by the Container Storage Interface (CSI) community. The design leverages container runtimes influenced by containerd and CRI-O, and interacts with observability ecosystems via integrations with Prometheus (software) for metrics and with logging systems akin to Fluentd and ELK Stack for telemetry. For orchestration of storage operations it employs controllers and operators conceptually related to patterns used by Operator Framework and platforms like OpenShift for lifecycle management. Networking and transport rely on kernel and user-space technologies comparable to those in projects such as Calico (software) and Weave Net when providing cross-node replication and data plane connectivity.

Use Cases and Deployments

Typical deployments address stateful workloads in Kubernetes clusters for databases, analytics, and CI/CD pipelines. Common application examples include running MySQL, PostgreSQL, and MongoDB in containerized form, as well as stateful processing for frameworks like Apache Spark and TensorFlow. Enterprises adopt the platform to enable persistent volumes for platforms provided by cloud providers such as Amazon Web Services, Microsoft Azure, and Google Cloud Platform, and for on-premises solutions integrated with virtualization stacks from vendors like VMware. Use cases extend to edge computing scenarios similar to those targeted by initiatives such as OpenEdge and to telecommunication environments adopting 5G infrastructure where low-latency storage matters.

Business and Funding

The company pursued a business model combining open source community projects with value-added commercial offerings, channel partnerships, and support services. Investors aligned with broader enterprise infrastructure funding trends participated in financing rounds alongside strategic backers experienced with storage and cloud startups. Funding and go-to-market strategies paralleled those used by comparable firms that commercialize open source storage software, and the company engaged with systems integrators and cloud service providers to expand deployments in sectors including finance, healthcare, and telecommunications.

Community and Open Source Contributions

The organization actively contributed to upstream cloud-native projects and maintained repositories under open source licenses, collaborating with developer communities that include contributors to Kubernetes, Prometheus (software), and etcd. The project hosted documentation, runbooks, and participated in events associated with the Cloud Native Computing Foundation and conferences such as KubeCon and Open Source Summit. Community-building activities included code contributions, bug triage, and participation in standards conversations around the Container Storage Interface (CSI) and other interoperability efforts.

Reception and Criticism

Reception among practitioners highlighted strengths in enabling stateful workloads on Kubernetes and in addressing data locality and performance challenges raised by distributed container platforms. Case studies from adopters in sectors like finance and telecommunication cited improvements in operational efficiency compared with legacy storage arrays from vendors such as NetApp and Dell EMC. Criticisms mirrored those leveled at other cloud-native storage projects: concerns about operational complexity for large-scale deployments, integration overhead compared with managed cloud-native block services from Amazon Web Services and Google Cloud Platform, and the need for mature tooling for backup, disaster recovery, and cross-cluster replication. Debates in the community referenced contrasts with architectural alternatives including distributed file systems like Ceph and orchestration strategies used by OpenShift and managed Kubernetes services.

Category:Software companies based in California