Technology
We choose what lasts, not what’s fashionable.
Technologies we run in production at every layer, and whose limits we know. Each choice has a reason.
Backend
- Go
- Echo
- gRPC
- Protobuf
- Node.js
- Python
- PHP
Web
- React
- TypeScript
- Vite
- TanStack Query
- ECharts
- Leaflet
Mobile
- Flutter
- Riverpod
- React Native
- Firebase
Data
- PostgreSQL
- Redis
- MongoDB
- MySQL
- Kafka
- RabbitMQ
- MinIO
Infrastructure
- Kubernetes
- Helm
- Docker
- Caddy
- nginx
- Cloudflare
Observability
- OpenTelemetry
- Prometheus
- VictoriaMetrics
- Grafana
- Loki
- Tempo
IoT
- MQTT
- EMQX
- Modbus
- Edge gateway
AI
- scikit-learn
- PyTorch
- pandas
- On-prem ML
Why
The reasons behind our choices.
Go, because it scales
One binary, low memory, strong concurrency. Most of our services are written in Go and run comfortably even on small servers.
PostgreSQL, because it’s reliable
From tenant isolation to job queues, we solve a lot in one well-known database — fewer moving parts, fewer failures.
Open standards, so you’re never locked in
OpenTelemetry, OpenAPI, MQTT, Kubernetes: your system is never tied to a single vendor.
Local AI, because the data is yours
Models are trained and served on your servers; sensitive data is never sent to a third-party API.
Let’s build your next system together.
Tell us about your idea, your current system or your bottleneck — we’ll come back with a realistic roadmap and timeline.