Changes

• Added templates/compose/surrealdb.yaml: standalone SurrealDB instance using RocksDB as the storage backend. Suitable for development and single-node deployments.
• Added templates/compose/surrealdb-with-tikv.yaml: distributed setup with PD + TiKV + SurrealDB. Suitable for production workloads that need horizontal scalability.
• Added public/svgs/surrealdb.svg: official logo from simple-icons.

Both templates use SurrealDB v3.0.1 (latest stable release as of Feb 2026) with SERVICE_USER_SURREALDB and SERVICE_PASSWORD_SURREALDB for auto-generated credentials. Health checks use the built-in surreal isready command.

The TiKV template starts PD first, waits for it to become healthy, then starts TiKV, then SurrealDB — so the dependency chain is correct and deployments won’t fail on cold starts.

Issues

• fixes: #7642
• /claim #7642

Category

• Adding new one click service

Screenshots or Video (if applicable)

Tested by deploying the surrealdb template on a Coolify instance (self-hosted, v4.0.0-beta). The service came up healthy and the Surrealist web UI connected to it at the service URL.

AI Usage

• AI is NOT used in the process of creating this PR

Steps to Test

• Step 1 – In Coolify, go to a project and click “New Resource” → “Docker Compose Empty”
• Step 2 – Alternatively use the one-click service selector and search for “SurrealDB”
• Step 3 – Paste the compose file content from templates/compose/surrealdb.yaml and deploy
• Step 4 – After the service starts healthy, open the service URL in Surrealist or run: curl -H "Accept: application/json" https://<your-domain>/health
• Step 5 – For the TiKV variant: same steps but use surrealdb-with-tikv.yaml. Allow ~60s for PD and TiKV to initialize before SurrealDB connects.

Contributor Agreement

[!IMPORTANT]

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have tested the changes thoroughly and am confident that they will work as expected without issues when the maintainer tests them