The systems we have built, the decisions behind their architecture and documented outcomes from client work.
Maborak product engineering
ASIN Watcher
Price monitoring combines recurring collection, regional price differences and timely notifications. A useful comparison must account for shipping and import fees, while collection workloads must stay separate from the customer application.
Separate collection from customer requests
TikRadar
Live-stream analytics must capture concurrent creator sessions, preserve events for later analysis and update viewers while sessions are still running. Ingestion and dashboard delivery have different lifecycles and capacity requirements.
Give ingestion its own lifecycle
LegalAI / PactoLegal
Legal research depends on locating relevant material and retaining its source. The system must ingest heterogeneous documents, retrieve useful passages and connect generated answers to the underlying legal corpus.
Keep retrieval separate from generation
Client work
Completed engagements with outcomes recorded in client reviews. Clients are identified by project type.
An application migration and server consolidation, with the result documented in a client review.
Read case study →An email sending engagement whose client reported resolving a problem that had persisted for over two years.
Read case study →Technologies we work with
Argo CD
Kubernetes
Docker
Podman
Ansible
Jenkins
Chef
Proxmox VE
Google Cloud
Linux
Red Hat
CentOS
NGINX
Apache
Traefik
Prometheus
Grafana
PostgreSQL
MySQL
MariaDB
Redis
etcd
Qdrant
Elasticsearch
Logstash
Kibana
PagerDuty
Go
Python
FastAPI
PHP
TypeScript
React
