Codync
A free, open-source 1:1 alternative to Grok Bot and Muse. Message Claude Code, Codex, Cursor and 40+ coding agents as persistent bots from your iPhone, Mac or Linux desktop. Group chats, threads, appr
Self-hosted GitHub Actions cache server written in Rust. Drop-in replacement for actions/cache, setup-* caches and BuildKit type=gha on self-hosted runners. 29 MB image, 3 MiB idle memory.
Developer toolsRust · Go TemplateGitHub @falcondev-ossOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Fast, memory-efficient self-hosted GitHub Actions cache server written in Rust. Drop-in replacement for the official cache, works with actions/cache unchanged. Supports S3, GCS, Azure Blob or filesystem storage with SQLite, Postgres or MySQL.
Taken from the repository README
Loading the full README.
Read the full README ↗A self-hosted, drop-in replacement for GitHub's cache service, written in Rust. Point your self-hosted runners at it and every actions/cache step, setup-* cache and docker buildx type=gha cache stays on your own hardware. No workflow changes.
| GitHub Actions Cache Server | |
|---|---|
| Image size | 29 MB |
| Startup to healthy | 0.5 s |
| Idle memory | 3 MiB |
| Upload (8 × 128 MiB, parallel) | 2.3 GiB/s |
| First download | 7.9 GiB/s |
| Lookups (64 concurrent) | 34,000/s, p99 7 ms |
| Small save + restore (256 KiB) | 1,143/s |
SQLite + filesystem on a Ryzen 9 5950X with NVMe. Reproduce with cargo run --release --example benchmark.
actions/cache, actions/setup-node & friends, BuildKit type=gha, any tool built on @actions/cache/metrics, /health, management API with OpenAPI docs1. Run the server
services:
cache-server:
image: ghcr.io/falcondev-oss/github-actions-cache-server
ports:
- '3000:3000'
environment:
API_BASE_URL: http://localhost:3000
volumes:
- cache-data:/app/.data
volumes:
cache-data:
2. Point your runners at it
Swap the runner image for our fork and set one variable:
image: ghcr.io/falcondev-oss/actions-runner:latest
env:
CUSTOM_ACTIONS_RESULTS_URL: http://cache-server:3000/
3. There is no step 3. Your workflows already use it.