nikitakarpei/my-yacy-node

A lightweight, composable reimplementation of a YaCy peer as small Go services

4

stars

486

commits

Go

primary language

Sep 9, 2026

updated

composable-architecture
distributed
golang
lightweight
microservices
nats-jetstream
p2p
search-engine
web-crawler
yacy

README

What this is

ci go license images

A lightweight reimplementation of a YaCy peer, built as small, single-purpose Go services.

“YaCy is a distributed Web Search Engine, based on a peer-to-peer network.” — YaCy FAQ

Start with Build your own search stack to see how to compose the services into working deployments.

Motivation

A standard YaCy node can exceed the memory available on small machines such as a Raspberry Pi, especially as the corpus grows. This project started with that constraint and became an experiment in a different way of building a YaCy peer.

Documentation

Each service under services/ and plugin under plugins/ has its own doc/ directory:

  • specification.md covers scope, requirements, and known limitations.
  • configuration.md covers operator-facing settings.

Project status

This project is under active development. It follows its own design instead of mirroring the Java version. Some features are not available yet, and others work differently.

Contributors

nikitakarpei

484 commits

claude

2 commits

nikitakarpei/my-yacy-node

A lightweight, composable reimplementation of a YaCy peer as small Go services

4

stars

486

commits

Go

primary language

Sep 9, 2026

updated

composable-architecture
distributed
golang
lightweight
microservices
nats-jetstream
p2p
search-engine
web-crawler
yacy

README

What this is

ci go license images

A lightweight reimplementation of a YaCy peer, built as small, single-purpose Go services.

“YaCy is a distributed Web Search Engine, based on a peer-to-peer network.” — YaCy FAQ

Start with Build your own search stack to see how to compose the services into working deployments.

Motivation

A standard YaCy node can exceed the memory available on small machines such as a Raspberry Pi, especially as the corpus grows. This project started with that constraint and became an experiment in a different way of building a YaCy peer.

Documentation

Each service under services/ and plugin under plugins/ has its own doc/ directory:

  • specification.md covers scope, requirements, and known limitations.
  • configuration.md covers operator-facing settings.

Project status

This project is under active development. It follows its own design instead of mirroring the Java version. Some features are not available yet, and others work differently.

Contributors

nikitakarpei

484 commits

claude

2 commits

Languages

Go

97.6%

Python

1.1%