8+ years
Continuous production runtime
Vulcan Ventures
Kraken: mission-critical infrastructure in production since 2017.
Built for real-world constraints: high throughput, massive outbound messaging, unreliable connectivity, zero data loss.
Proof
Production scale, measured every day.
Kraken has run continuously since 2017, with telemetry that exposes throughput, latency, and resilience under load.
100M+
Transactions processed per month
10M+
System emails delivered per month
20-500 TPS
Sustained throughput under load
Sub-second
Latency across critical paths
How it works
Main-DB-first, with offline continuity built in.
Kraken is designed for environments where networks fail and data must stay consistent.
- Remote Agent: a standalone microservice with its own local database for offline operation.
- Core platform: microservices that prioritize correctness and predictable write paths.
- Synchronization: replay-safe reconciliation that prevents duplicate or lost writes.
- Data layer: PostgreSQL as the system of record for transactional integrity.
Features
Engineering choices that hold under pressure.
Kraken exists because it solved real production constraints and continues to validate architectural trade-offs.
Main-DB-first architecture
- PostgreSQL as the authoritative transactional ledger.
- Scale designed to support hundreds of millions of monthly writes.
- Transactional workflows separated from high-volume email pipelines.
Remote Agent continuity
- Standalone microservice with its own local database.
- Buffers writes during outages; syncs when connectivity returns.
- Main-DB-first reconciliation to prevent duplication.
Operational telemetry
- Throughput, queue depth, latency percentiles, and error rates.
- Signals guide capacity planning and refactoring decisions.
- Validated daily against real traffic spikes.
Controlled infrastructure
- Containerized deployments without unnecessary orchestration overhead.
- Predictable runtime behavior and controlled releases.
- Stability prioritized over novelty.
What this means for Vulcan clients
We live with our engineering decisions. Kraken proves what happens after launch.
- We understand the long-term cost of technical debt.
- We design systems meant to survive years of change.
- We prioritize maintainability over shortcuts.
Evidence, not a pitch
Kraken demonstrates Vulcan's ability to:
- Design systems for scale and failure.
- Make explicit architectural trade-offs.
- Operate and evolve software over long lifecycles.
Technology choices
Full microservice architecture
Independent services with clear boundaries and controlled deployments.
Golang
Primary backend services where throughput and predictable latency matter.
Java
Reliable JVM services for long-lived transaction workflows.
Node.js
Event-driven services and integrations with external systems.
Angular
Enterprise-grade UI with a consistent component system.
Every component exists because it solved a production problem.
Evolution timeline
2017-2024
2017
Initial production launch.
2019
Architectural refactor toward microservices.
2021
Version 2 government compliance, increased security, and new functionality.
2022
Remote Agent and sync engine maturity.
2024
Sustained hundreds of millions of monthly transactions.
Public record
Kraken has been publicly accessible under the kraken.bo domain since 2017.
View first public snapshot (Internet Archive)
Live system: https://kraken.bo (authentication required)
Talk to Vulcan about your product.
Plan for scale, resilience, and years of growth with a senior team that already operates mission-critical systems.