Datarocks/ open source
oss.datarocks.ch

Open source
at Data Rocks

The tooling we build for our own platform work — published under the MIT license, so you can run it in your stack too.

Browse projectsgithub.com/datarocks-ag

Projects

Collections of tools that share a purpose and a way of working — and standalone projects.

COLLECTION · 6 TOOLS

Provisioners

Declarative, idempotent bootstrapping for the services your stack depends on. One small Go binary per service — describe what should exist, run it as an init container, and your app starts against a ready environment.

View collection →
Keycloakv1.13.0realms, clients, protocol mappers, roles, usersPostgreSQLv2.0.0roles, databases, schemas, privileges, extensionsNATSv1.1.0streams, consumersRedpandav2.0.0topics, schemas, SASL users, ACLsGCP emulatorsv2.0.1Pub/Sub topics, subscriptions, Cloud Storage bucketsSeaweedFSv1.0.0S3 buckets, IAM identities, bucket policies, lifecycle rules
PROJECT

go-egress-mitm-proxy

v4.1.1

A MITM HTTP/HTTPS proxy that implements split-brain DNS for egress traffic control in containerised environments. Decide per host where traffic goes, what gets through and which headers travel with it.

  • Kubernetes sidecar
  • outbound HTTP/2
View project →
  • github.comallowed
  • api.production.com → 10.20.30.40rewritten
  • ads.tiktok.com403 blocked

How we build

Every project we publish follows the same engineering baseline.

01

Declarative

Behaviour lives in one plain YAML file you can review, diff and version. Your config is the documentation of your environment.

02

Safe by default

Provisioners never remove what they did not create; the proxy blocks what is not allowed. Defaults fail closed, not open.

03

Observable

Structured logs, Prometheus metrics and health endpoints where they matter. No silent failures.

04

Shipped properly

CI on every repo, container images on ghcr.io, semantic versions with release notes.

Data Rocks AG

[ONE OR TWO LINES ON WHAT DATA ROCKS DOES AND FOR WHOM]

Visit datarocks.ch →