RKSSH LLP · Engineering Blog
20 articles · updated regularly
Jenkins still powers 40% of CI/CD in production. GitHub Actions is eating the rest. Here's a clear-eyed comparison - including when Jenkins is the right answer and when it's legacy debt.
Most EKS clusters run entirely on On-Demand instances and overpay by 60% or more. Here's the exact setup - Karpenter node pools, spot interruption handling, and workload placement - that we use to reduce bills without touching application code.
Running LLMs in production is an infrastructure problem as much as an AI problem. Here's the exact setup - GPU node pools, vLLM on Kubernetes, autoscaling, and request routing - that we use to put language models into production for AI startups.
Three strategies, three trade-offs. Which deployment pattern is right for your team depends on your risk tolerance, infrastructure budget, and how fast you want to detect problems. Here's the honest breakdown with working configs.
Kubernetes Secrets are base64-encoded, not encrypted. Most startups find this out after a security review. Here's how to actually manage secrets in production - and which tool fits which team size.
kubectl apply in production is an antipattern. GitOps solves the core problem: making your Git repository the single source of truth for what is running in your cluster. Here's a complete ArgoCD setup from scratch.
Most startup Kubernetes clusters have monitoring that detects problems after users report them. Here's how to set up the full observability stack - metrics, logs, and alerts - that catches issues before they reach users.
80% of large engineering orgs now have platform teams. But most startups implement platform engineering too early - or too late. Here's the clear signal that tells you when to invest and what to build first.
A practical guide to CI/CD pipeline setup for startups. Which tools to pick, how to structure your pipeline, what a working GitHub Actions config looks like, and what to avoid.
Security reviews at startups typically happen after something goes wrong. DevSecOps moves security earlier - into the CI pipeline, not the post-incident review. Here's a practical setup that catches vulnerabilities before they reach production.
Cloud cost overruns are not a finance problem - they are an engineering problem. Here's how engineering teams take ownership of cloud spend: the metrics to track, the tooling to use, and the decisions that cut 30–50% of the bill.
An honest comparison of ECS and Kubernetes for startups. Team size, complexity trade-offs, migration cost, and a clear decision framework from engineers who have set up both.
Most cloud decisions are made by whoever set up the first EC2 instance three years ago. Here's a structured comparison for startups that have not committed yet - or are considering a migration.
SOC2 Type II takes 6–12 months and most engineering teams dread it. It does not have to be painful. Here's how to structure the technical controls so compliance becomes an output of your existing engineering practices, not extra work on top.
A direct comparison of the three most-used infrastructure-as-code tools in 2026. Which one fits your team depends on who writes it, not which one has more stars on GitHub.
Manual deployments don't just cost time. They cost engineering hours, shipping velocity, and morale. Here is the full cost calculation - and why most CTOs underestimate it.
Most cloud overspend comes from five fixable misconfigurations. You do not need to refactor anything - you need to look in the right places.
Most ML projects stall at the notebook stage not because the model is bad but because the infrastructure to serve, monitor, and retrain it does not exist. Here is how to build it.
ISO 27001 is the most commonly requested security certification for enterprise B2B deals. Here is a realistic picture of what the process looks like, how long it takes, and what the technical work involves.
Kubernetes is not always the answer. Here is how to decide whether your team needs it now, and what the migration actually looks like when you do.