wesql

WeSQL: Run MySQL with S3-Backed Storage

WeSQL is a MySQL distribution that stores database data in S3-compatible object storage, separating compute from storage. It is aimed at teams seeking portable, cost-conscious MySQL for serverless or bring-your-own-cloud deployments.

View on GitHub Compare
Stars
843
Forks
35
Stars, last 30 days
-1

Our take

Health score

45/100

How it is scored
Activity
37
Community
59
Issues
21
Pull requests
64

-1 stars in the last 30 days

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

840

Forks

34

Change since Nov 15, 2026: 0 stars·0 forks

Overview

WeSQL is a MySQL distribution that replaces traditional disk-based data storage with S3 or S3-compatible object storage. By separating compute from storage, it is designed to let a database instance connect to stored data and begin serving without additional data setup.

It may suit teams that want MySQL compatibility while choosing their own cloud storage environment. The project describes use in serverless and bring-your-own-cloud (BYOC) settings, as well as development and testing.

Key Features

  • MySQL distribution with compute-storage separation.
  • Stores database data as objects in S3 or S3-compatible systems.
  • Includes binlogs, schemas, storage-engine metadata, WAL, and data files in its object-storage approach.
  • Designed to start an empty instance, connect to S3, load data, and serve it.
  • Intended to run on different clouds without vendor lock-in.
  • Documentation includes architecture, tutorials, and binary installation guidance.

Use Cases

  • Teams developing or testing applications that need a MySQL-compatible database backed by object storage.
  • Operators exploring serverless database deployments where compute and storage are managed separately.
  • Organizations planning a BYOC setup that keeps storage in their chosen cloud environment.
  • MySQL users seeking to evaluate object-storage-backed data durability and operational trade-offs.

Getting Started

Start with the binary installation guide. For build instructions and more detail, see the repository README and WeSQL documentation.

Considerations

  • A compatible S3 service is central to the storage design, so deployment requires access to S3 or an S3-compatible system.
  • The repository specifies GPLv2 only, without an any-later-version clause. Review the license requirements before adopting it.
  • The supplied README encourages trying WeSQL in development and testing environments. Evaluate operational fit before relying on it for production workloads.
  • The repository does not provide a build command in the supplied README; use its linked compilation guide for instructions.

Found this useful?

Share it with someone who would like WeSQL.