diff --git a/deploy/atomicassets/.env.example b/deploy/atomicassets/.env.example
index 0d0f470..87db09e 100644
--- a/deploy/atomicassets/.env.example
+++ b/deploy/atomicassets/.env.example
@@ -22,3 +22,11 @@ WORMDB_WIRE_PORT=6389
 
 # Mongo WiredTiger cache (GiB).
 MONGO_CACHE_GB=2
+
+# Path to the `wormdb` repo (for building the aa-feed image), RELATIVE to deploy/atomicassets. Default
+# assumes wormdb is a SIBLING of this repo (…/wormdb beside …/hyperion-tools). Override for other layouts.
+WORMDB_DIR=../../../wormdb
+
+# aa-feed start block. Default = the snapshot block; the feed clamps up to the node's SHiP retention if
+# that block is older than the node still serves (the gap is the Phase-3 archive backfill's job).
+FEED_START=269541093
diff --git a/deploy/atomicassets/docker-compose.yml b/deploy/atomicassets/docker-compose.yml
index bfa255b..33224cc 100644
--- a/deploy/atomicassets/docker-compose.yml
+++ b/deploy/atomicassets/docker-compose.yml
@@ -72,6 +72,7 @@ services:
       AA_SEGMENT: /data/aa.wseg
     volumes:
       - aa-data:/data
+      - aa-wormdb-data:/var/lib/wormdb # WAL + snapshot (persistence:full) → overlay survives a restart
       - ./wormdb.json:/etc/wormdb.json:ro
     # Loopback-only. 6390 = HTTP read API (curl from the host); 6389 = WormWire (privileged exec/peer
     # wire) — the Phase-2 SHiP feed reaches it over the bridge, so neither needs off-host exposure.
@@ -85,10 +86,49 @@ services:
         condition: service_completed_successfully
     networks: [aa-stack]
     profiles: ["state", "all"]
+    healthcheck:
+      # the bun feed (aa-feed) waits on this; the wormdb image ships curl, so probe the HTTP gateway.
+      test: ["CMD-SHELL", "curl -fsS http://127.0.0.1:6390/atomicassets/v1/config >/dev/null || exit 1"]
+      interval: 5s
+      timeout: 4s
+      retries: 30
+      start_period: 8s
+
+  # Phase 2: bun SHiP feed — keeps the overlay live from the Jungle 4 node (host.docker.internal). Built
+  # from the wormdb bun app; EXECs aa_mint/aa_transfer/aa_burn over WormWire into wormdb-aa:6389.
+  # In the "all" profile only (NOT a standalone "feed" profile): it depends_on wormdb-aa, which is in
+  # state/all, so a `--profile feed`-only project would reference an ignored service and be invalid. Run
+  # the live stack with `docker compose --profile all up`; attach just the feed to a running state stack
+  # with `docker compose --profile all up -d aa-feed` (the named service resolves its deps without
+  # restarting them); `docker compose --profile state up` serves the static snapshot without the feed.
+  aa-feed:
+    build:
+      # Default assumes `wormdb` is a SIBLING of this repo (…/hyperion-tools + …/wormdb). For a different
+      # layout, set WORMDB_DIR in .env to the wormdb repo path relative to this compose file's directory.
+      context: ${WORMDB_DIR:-../../../wormdb}/apps/bun
+      dockerfile: Dockerfile.feed
+    image: aa-stack/feed:latest
+    container_name: aa-feed
+    restart: on-failure
+    environment:
+      SHIP: ws://host.docker.internal:28080/
+      CHAIN_API: http://host.docker.internal:28888
+      CHAIN: ${CHAIN:-jungle4}
+      AA_CONTRACT: atomicassets
+      WORMHOST: wormdb-aa
+      PORT: "6389"
+      START: ${FEED_START:-269541093} # snapshot block; the per-block checkpoint overrides on restart
+    extra_hosts: *host_gw
+    depends_on:
+      wormdb-aa:
+        condition: service_healthy
+    networks: [aa-stack]
+    profiles: ["all"]
 
 volumes:
   mongo-data:
   aa-data:
+  aa-wormdb-data:
 
 networks:
   aa-stack:
diff --git a/deploy/atomicassets/wormdb.json b/deploy/atomicassets/wormdb.json
index 418ba0d..4ed9a25 100644
--- a/deploy/atomicassets/wormdb.json
+++ b/deploy/atomicassets/wormdb.json
@@ -1,6 +1,6 @@
 {
   "data": "/var/lib/wormdb",
-  "store": { "persistence": "none" },
+  "store": { "persistence": "full" },
   "server": { "port": 6389 },
   "gateway": { "enabled": true, "port": 6390 },
   "auth": { "require_auth": false }