Pull.
Run. Done.
Every WeftKit component ships as a self-contained Docker image. Pull, mount a volume, and you are running a production-grade database engine. Free to use. Closed source. No license key required.
latest tag. All images are published under the weftkit/ namespace.Service Registry
weftkit/discovery:0.1.0
Central service discovery and health monitoring with gRPC, REST, and a web dashboard.
Default Ports
Pull
docker pull weftkit/discovery:0.1.0Run
docker run -d \
--name weftkit-discovery \
-p 20150:20150 \
-p 20151:20151\
-v discovery-data:/var/lib/weftkit/discovery \
weftkit/discovery:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/discovery
WEFTKIT_DASHBOARD=true
WEFTKIT_NO_AUTH=trueRelational Database
weftkit/relational:0.1.0
PostgreSQL v3 wire protocol database server supporting SQL queries and transactional operations.
Default Ports
Pull
docker pull weftkit/relational:0.1.0Run
docker run -d \
--name weftkit-relational \
-p 20000:20000 \
-p 9100:9100 \
-p 9090:9090\
-v relational-data:/var/lib/weftkit/data \
weftkit/relational:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataDocument Database
weftkit/document:0.1.0
MongoDB wire protocol database server supporting document-oriented queries and aggregations.
Default Ports
Pull
docker pull weftkit/document:0.1.0Run
docker run -d \
--name weftkit-document \
-p 20001:20001 \
-p 9100:9100 \
-p 9090:9090\
-v document-data:/var/lib/weftkit/data \
weftkit/document:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataGraph Database
weftkit/graph:0.1.0
Bolt v4+ wire protocol for graph/network queries with traversals and pattern matching.
Default Ports
Pull
docker pull weftkit/graph:0.1.0Run
docker run -d \
--name weftkit-graph \
-p 20002:20002 \
-p 9100:9100 \
-p 9090:9090\
-v graph-data:/var/lib/weftkit/data \
weftkit/graph:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataIn-Memory Cache
weftkit/inmemory:0.1.0
Redis RESP3 wire protocol for ultra-fast key-value caching and session storage.
Default Ports
Pull
docker pull weftkit/inmemory:0.1.0Run
docker run -d \
--name weftkit-inmemory \
-p 20003:20003 \
-p 9100:9100 \
-p 9090:9090\
-v inmemory-data:/var/lib/weftkit/data \
weftkit/inmemory:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataKey-Value Store
weftkit/keyvalue:0.1.0
DynamoDB REST wire protocol for distributed key-value operations with strong consistency.
Default Ports
Pull
docker pull weftkit/keyvalue:0.1.0Run
docker run -d \
--name weftkit-keyvalue \
-p 20004:20004 \
-p 9100:9100 \
-p 9090:9090\
-v keyvalue-data:/var/lib/weftkit/data \
weftkit/keyvalue:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataVector Database
weftkit/vector:0.1.0
gRPC Pinecone-compatible vector store for semantic search and similarity operations.
Default Ports
Pull
docker pull weftkit/vector:0.1.0Run
docker run -d \
--name weftkit-vector \
-p 20005:20005 \
-p 9100:9100 \
-p 9090:9090\
-v vector-data:/var/lib/weftkit/data \
weftkit/vector:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataMarkdown Store
weftkit/markdown:0.1.0
Custom REST API for Markdown documents with full-text search and content navigation.
Default Ports
Pull
docker pull weftkit/markdown:0.1.0Run
docker run -d \
--name weftkit-markdown \
-p 20006:20006 \
-p 9100:9100 \
-p 9090:9090\
-v markdown-data:/var/lib/weftkit/data \
weftkit/markdown:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataFile / Object Store
weftkit/filestore:0.1.0
S3 REST wire protocol for object storage, large file handling, and content-addressable access.
Default Ports
Pull
docker pull weftkit/filestore:0.1.0Run
docker run -d \
--name weftkit-filestore \
-p 20007:20007 \
-p 9100:9100 \
-p 9090:9090\
-v filestore-data:/var/lib/weftkit/data \
weftkit/filestore:0.1.0Environment
WEFTKIT_DATA_DIR=/var/lib/weftkit/dataAPI Gateway
weftkit/gateway:0.1.0
Multi-protocol router (TCP binary, gRPC, GraphQL) providing unified access to all database engines.
Default Ports
Pull
docker pull weftkit/gateway:0.1.0Run
docker run -d \
--name weftkit-gateway \
-p 20100:20100 \
-p 20101:20101 \
-p 20102:20102 \
-p 20103:20103 \
weftkit/gateway:0.1.0Environment
WEFTKIT_ADMIN_PORT=20103Connection Pool
weftkit/pool:0.1.0
Wire-protocol connection multiplexer and load balancer with pooling and failover.
Default Ports
Pull
docker pull weftkit/pool:0.1.0Run
docker run -d \
--name weftkit-pool \
-p 20160:20160 \
weftkit/pool:0.1.0Environment
No required env varsInteractive Playground
weftkit/playground:0.1.0
Web UI for query editing, visualization, streaming changes, and exploring all database engines.
Default Ports
Pull
docker pull weftkit/playground:0.1.0Run
docker run -d \
--name weftkit-playground \
-p 20170:20170 \
weftkit/playground:0.1.0Environment
WEFTKIT_PLAYGROUND_BIND_ADDRESS=0.0.0.0:20170Full Stack in One File
A typical starter stack: Discovery + Relational + In-Memory + Gateway + Playground. Save as docker-compose.yml and run `docker compose up -d`.
# docker-compose.yml — typical stack
services:
discovery:
image: weftkit/discovery:0.1.0
ports: ["20150:20150", "20151:20151"]
volumes: [discovery-data:/var/lib/weftkit/discovery]
environment:
WEFTKIT_DASHBOARD: "true"
WEFTKIT_NO_AUTH: "true"
relational:
image: weftkit/relational:0.1.0
ports: ["20000:20000", "9100:9100"]
volumes: [rel-data:/var/lib/weftkit/data]
inmemory:
image: weftkit/inmemory:0.1.0
ports: ["20003:20003", "9101:9100"]
volumes: [mem-data:/var/lib/weftkit/data]
gateway:
image: weftkit/gateway:0.1.0
ports: ["20100:20100", "20101:20101", "20102:20102", "20103:20103"]
depends_on: [discovery, relational, inmemory]
playground:
image: weftkit/playground:0.1.0
ports: ["20170:20170"]
environment:
WEFTKIT_PLAYGROUND_BIND_ADDRESS: "0.0.0.0:20170"
volumes:
discovery-data:
rel-data:
mem-data:Full deployment documentation lives in the Deployment Guide.
How WeftKit Is Distributed
- Docker images only. No tarballs, no installers, no package-manager uploads. Every component is pulled from the WeftKit container registry.
- Free to run. No license key, no usage ceiling, no mandatory telemetry. Pull an image, run it, and it just works.
- Closed source. The binaries inside the images are final. The source code is not distributed in any form — no public repository, no crates.io publication, no source bundle.
- Standard wire protocols. Every engine answers a widely-supported wire protocol (PostgreSQL, Redis, Mongo, Bolt, S3, DynamoDB, gRPC, REST). You do not need a WeftKit-specific driver.