CYBERPUNK TECHNOLOGY

sudo make it work

We build and repair the systems that carry the load: backends, integrations and the security around them.

[ start a project ]$ cat services.txt

// java · spring · postgres · k8s · aws · 11 years in production

services

// 4 fronts
~/backend

backend engineering

High-scale backends, APIs and integrations. Java/Spring Boot, PostgreSQL, Kubernetes, AWS. Foundation first, ornament never.

$ man backend →
~/cto-as-a-service

cto as a service

Technical leadership on contract. Architecture decisions, stack modernization, hiring bar, and the roadmap that survives contact with production.

$ man cto-as-a-service →
~/security

security engineering

AppSec, security reviews, DevSecOps and zero-trust architecture. Threat models that name the attacker, controls that survive an audit.

$ man security →
~/products

own products

Tools and SaaS built in-house. Same standard as client work, with our name on the incident.

$ ls products →

selected work

$ ls -la ./projects
~/projects/logistics-platform

logistics platform rework

// logistics

Monolithic scheduling core blocked releases; deploys took a weekend and a rollback plan nobody trusted.

deploy window 48h → 12min, rollback automated, zero downtime cutover

  • architecture
  • migration
  • kubernetes
  • NDA
~/projects/payments-latency

payments api latency

// fintech

Checkout API degraded under peak load; p95 above 1.8s and retries amplifying the queue.

p95 1.8s → 210ms, retry storm eliminated, no new infrastructure cost

  • java
  • postgres
  • k8s
  • OPEN SOURCE
$ cat payments-latency.md →

$ ls ./projects/public → 1 result. The rest is under NDA. That is the point.

how we work

$ man cyberpunk
CYBERPUNK(7)Operator's ManualCYBERPUNK(7)
NAME
cyberpunk-technology — build systems that survive production
SYNOPSIS
cyberpunk [--backend] [--cto] [--security] [--products]
DESCRIPTION
Decisions are written down before they are built, with the trade-off and the rejected alternative next to them.
Scope is what was agreed. When an estimate turns out wrong, the estimate changes and you hear about it the same week, not at delivery.
Security is a premise, not a feature. Every system assumes someone will try to break it.
SEE ALSO
services(7) · work(7) · contact(1)

stack

$ tree ~/stack
  • backend engineeringjava · spring boot · postgres · k8s · aws
  • cto as a servicearchitecture · code review · hiring · roadmap
  • security engineeringappsec · devsecops · zero trust · threat modeling

writing

$ ls ./posts

$ ls ./posts → 0 results. Nothing published yet.

contact

$ mail -s

Tell us what is broken, what you are building, or what needs a review. Response in under 24 hours, from a person.

hello@cyberpunktechnology.com.br

info:no newsletter, no drip campaign, no sales sequence.
~/contact/new.msg