Dokploy / Dokploy/dokploy

Add First-Class ScyllaDB Support as a Managed Database in Dokploy

Open
#2,746 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Dokploy already makes it easy to deploy popular databases like Postgres or MySQL, but for high-throughput, low-latency applications there’s no built-in option for ScyllaDB. This means developers who want to use ScyllaDB need to manage it completely outside of Dokploy, losing the “all-in-one” experience that makes Dokploy attractive.

Describe the solution you'd like

Add first-class support for ScyllaDB as a managed service within Dokploy. Ideally, this would allow:

  • One-click provisioning of ScyllaDB nodes
  • Easy scaling by adding/removing nodes
  • Automatic replication and fault tolerance configuration
  • Integration with the UI/CLI for monitoring cluster health and resources
Describe alternatives you've considered

Currently, the only way is to run ScyllaDB manually with Docker or use Scylla Cloud, but both approaches break the seamless workflow Dokploy provides.

Additional context

ScyllaDB is a highly performant, Cassandra-compatible database known for handling millions of operations per second at low latencies while being far more resource-efficient than traditional options. Supporting it would give Dokploy users a modern, future-proof database option for projects that start small but need to scale massively (real-time analytics, IoT, time-series, gaming backends, etc.).

This aligns perfectly with Dokploy’s goal of supporting projects that “grow with you.” Adding ScyllaDB would also help Dokploy stand out from other platforms that only ship with the usual suspects like Postgres or MySQL.

Website: https://www.scylladb.com
Repository: https://github.com/scylladb/scylladb

Will you send a PR to implement it?

Maybe, need help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how Dokploy currently provisions managed databases and how those services connect to the UI and CLI. Define the scope for one-click ScyllaDB node provisioning, scaling, replication and fault tolerance, plus cluster health and resource monitoring; done means these requested capabilities work as an integrated managed service.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
databases, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.