diff --git a/blueprints/spacetimedb/docker-compose.yml b/blueprints/spacetimedb/docker-compose.yml
new file mode 100644
index 00000000..05d85869
--- /dev/null
+++ b/blueprints/spacetimedb/docker-compose.yml
@@ -0,0 +1,13 @@
+version: "3.8"
+services:
+  spacetimedb:
+    image: clockworklabs/spacetime:v2.6.1
+    restart: unless-stopped
+    command: start
+    ports:
+      - 3000
+    volumes:
+      - spacetimedb-data:/home/spacetime
+
+volumes:
+  spacetimedb-data: {}
diff --git a/blueprints/spacetimedb/instructions.md b/blueprints/spacetimedb/instructions.md
new file mode 100644
index 00000000..676ced23
--- /dev/null
+++ b/blueprints/spacetimedb/instructions.md
@@ -0,0 +1,45 @@
+# SpacetimeDB
+
+SpacetimeDB is a database and server runtime in one: your clients connect directly to the database and your application logic runs inside it as WebAssembly modules. There is no web UI — the domain assigned to this service exposes the SpacetimeDB HTTP/WebSocket API (so opening `/` in a browser returns a plain 404; that is expected).
+
+## Verify the server is running
+
+```bash
+curl -i https://your-domain.com/v1/ping
+```
+
+A `200 OK` response means the server is up.
+
+## Connect with the SpacetimeDB CLI
+
+1. Install the CLI on your local machine:
+
+   ```bash
+   curl -sSf https://install.spacetimedb.com | sh
+   ```
+
+2. Register your Dokploy instance as a server and make it the default:
+
+   ```bash
+   spacetime server add --url https://your-domain.com dokploy --default
+   ```
+
+3. Log in (or create an anonymous local identity) and publish a module:
+
+   ```bash
+   spacetime login
+   spacetime publish --server dokploy my-database
+   ```
+
+4. Check connectivity at any time:
+
+   ```bash
+   spacetime server ping dokploy
+   ```
+
+From your game or app, connect with any SpacetimeDB client SDK (Rust, C#, TypeScript) using `https://your-domain.com` as the host URI. See the [getting started guide](https://spacetimedb.com/docs/getting-started) for a full walkthrough.
+
+## Notes
+
+- All server state (databases, logs and the JWT signing keys used for identities) is persisted in the `spacetimedb-data` volume, so identities survive restarts and upgrades.
+- Client connections use WebSockets over the same domain; no extra configuration is needed.
diff --git a/blueprints/spacetimedb/logo.png b/blueprints/spacetimedb/logo.png
new file mode 100644
index 00000000..77099a12
Binary files /dev/null and b/blueprints/spacetimedb/logo.png differ
diff --git a/blueprints/spacetimedb/meta.json b/blueprints/spacetimedb/meta.json
new file mode 100644
index 00000000..824840ef
--- /dev/null
+++ b/blueprints/spacetimedb/meta.json
@@ -0,0 +1,17 @@
+{
+  "id": "spacetimedb",
+  "name": "SpacetimeDB",
+  "version": "v2.6.1",
+  "description": "SpacetimeDB is a relational database with a built-in server runtime. Clients connect directly to the database and run server-side logic (modules) inside it, making it ideal for real-time multiplayer games, chat and collaborative applications without a separate backend.",
+  "logo": "logo.png",
+  "links": {
+    "github": "https://github.com/clockworklabs/SpacetimeDB",
+    "website": "https://spacetimedb.com/",
+    "docs": "https://spacetimedb.com/docs"
+  },
+  "tags": [
+    "database",
+    "realtime",
+    "backend"
+  ]
+}
diff --git a/blueprints/spacetimedb/template.toml b/blueprints/spacetimedb/template.toml
new file mode 100644
index 00000000..35d00d6f
--- /dev/null
+++ b/blueprints/spacetimedb/template.toml
@@ -0,0 +1,8 @@
+[variables]
+main_domain = "${domain}"
+
+[config]
+[[config.domains]]
+serviceName = "spacetimedb"
+port = 3000
+host = "${main_domain}"