Skip to content
View lumarispro's full-sized avatar

Block or report lumarispro

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
lumarispro/README.md

Lumaris — Infrastructure, kept in steady light.

lumaris.space  ·  lumarispro@gmail.com  ·  Discord

Lumaris designs and operates the layer underneath your product: bare-metal cloud, platform automation and observability, run by engineers who treat uptime as a craft. Our own fleet of dedicated servers runs in European data centres.

The stack

We think about infrastructure as layers, each one resting on the one below. Every layer has a repository: the tooling we use to run it ourselves, published as it is.

Layer 04 · Network nodes · lava-provider Layer 03 · Observability · lava-provider-exporter, grafana-dashboards Layer 02 · Platform · server-bootstrap Layer 01 · Metal · lumaris.space

Layer Repository What's inside
04 lava-provider Install, service unit, TLS proxy and status scripts for our Lava RPC provider
03 lava-provider-exporter Prometheus exporter for a provider's on-chain state: stake, delegations, jails, per spec
03 grafana-dashboards Dashboards and alert rules for hosts and the Lava provider
02 server-bootstrap Ansible roles that turn a fresh bare-metal host into a hardened, monitored node
01 lumaris.space Source of our website

On public chains

Blockchain nodes are demanding infrastructure: they never stop syncing, and their performance is measured in public. We run them with the same hardware, automation and monitoring as everything else.

Lumaris on Lava Network: RPC provider for 31 specs

How we work

  1. Design for failure. Redundancy where it matters, simplicity everywhere else.
  2. Automate the routine. Provisioning, patching and recovery are code.
  3. Measure everything. If it isn't observed, it isn't operated.

© 2026 Lumaris · Europe

Pinned Loading

  1. lava-provider-exporter lava-provider-exporter Public

    Prometheus exporter for a Lava Network provider's on-chain state: stake, delegations, jails and reported blocks per spec.

    Python 1

  2. lava-provider lava-provider Public

    How the Lumaris RPC provider on Lava Network is installed and operated: lavap install, systemd, nginx TLS proxy, status scripts.

    Shell