Three people who have been on the other side of the AWS bill.
CEO & Co-Founder
Previously lead infrastructure engineer at a Series B SaaS company where he managed 14 AWS accounts and $2.4M in annual cloud spend. Spent six weeks manually auditing CloudWatch data before writing the first version of what became KernelRun. Holds an MS in Computer Science from Georgia Tech.
CTO & Co-Founder
Former staff engineer at a cloud infrastructure tooling company where she built the resource discovery pipeline that served 800 enterprise accounts. Designed KernelRun's metric ingestion architecture and the tag inference model. Seven years working on distributed systems at scale across AWS and GCP.
Head of Customer Engineering
Spent four years as a cloud architect at a consulting firm, running FinOps engagements for mid-market companies. Has personally reviewed CloudWatch data for over 90 AWS accounts. Leads onboarding and integration support for KernelRun customers.
Core team is in Palo Alto. We hire for specific roles without geography requirements when the work suits it. All hands happen weekly. Engineering discussions happen in writing.
Everyone on the team has operated cloud infrastructure. Customer conversations happen with engineers, not account managers. We do not hire for roles that exist to describe what other people build.
Meetings have a written agenda. Decisions are documented. We operate across two time zones. Async-first means everyone's working hours are their own — and the context is always available when you need it.
Looking for a backend engineer with experience in AWS cost tooling or CloudWatch APIs. If you have built something similar and found it frustrating, that is the right background. Reach us at info@kernelrun.com.
Demos are run by engineers, not sales staff. Bring your CloudWatch questions.
Request a Demo