Users showed up, the product found its footing, and people now count on it staying up. What got it built quickly isn't what keeps it running, and the gap tends to show itself as an outage, a security question you can't answer, or a bill nobody can explain.
That is a win worth scaling. Scaling it takes engineering, and that is where I come in.
I work in the stacks AI tools tend to produce, React, Next.js, and TypeScript, and in the Go, Rails, Swift, and Kubernetes systems around them.
Architecture ready for many usersBuilt to hold up under real load, not only on a diagram
Real securityWho can get in, what they can reach, and what a breach would cost you
Practices that keep it dependableAs the product and the team grow
Care model
How I care for your software
From a first checkup to ongoing operations. Start wherever you are.
Start here
The checkup
A Production Readiness Assessment: a senior engineer reads your product the way production will, and tells you plainly what to do first.
Architecture, security, data handling, deployment, and development practices
Reviewed by the engineer who does the work that follows
A plain-English report
A prioritized roadmap you own, regardless of what follows
An executive readout
Primary care
Fractional CTO support by the month
A senior engineer in the room for the decisions that are expensive to reverse
Security and architecture reviewed as the product changes
Mentorship for you and whoever is building alongside you
Treatment
Engineering work from your roadmap
Production databases: backups, migrations, and the failure modes nobody tested
Authentication, access control, and environments that stay separate
Deployment pipelines that make a release routine
Ongoing care
Managed hosting, monitoring, and on-call for launches
Monitoring, so a problem is found before your users report it
On-call through a launch or a traffic spike
Operated by Onyx Edge, which has run managed hosting since 2020
Track record
Engineering practice, earned on real products
Twenty years of products built with conventional engineering practice, and for the last two years an AI-augmented workflow on top of it. The practices that keep software maintainable are what make building with AI fast and safe, and it is the workflow I bring to your product.
Between 2009 and 2014, apps I built for iOS, Android, and the web went from nothing to millions of users and more than four years in the top charts, on a back end I designed, built, and scaled alone to nearly 30 million requests a month.
Products with paying users
A real-time analytics SaaS, a job-matching product on Go and Kubernetes, and an API sold with access tokens and usage billing. The parts you are about to need, already built once.
Still shipping
Visiting Objects is a production SaaS platform for publishers: Go microservices on Kubernetes, built and operated today by the same person who reviews your product.
Products I have built and run
2022 to nowVisiting Objects. Site search, analytics, and AI-readable content for publishers.
2016 to 2018StackPair. Skill-based job matching for technical professionals, on iOS and the web.
2015 to 2016360gram. An iOS and web app for interactive panoramas and 360 degree views.
2012Post Heat. A SaaS that analyzed social networks in real time to find the best times to post.
2009 to 2014Top-chart apps. On iOS, Android, and the web. Millions of users, 4+ years in the top charts, nearly 30 million requests a month.
AlsoReverse Geocoding API. An API as a service with token management and usage-based billing.
AlsoPost Alert. A Slack app, listed in the Slack App Directory.
Who's behind it
I'm Luke Heuer. Vibe Hospital is Onyx Edge's practice for AI-built products. I have been a professional software engineer since 2004, with full-time roles in backend, frontend, full-stack, and infrastructure engineering, a web agency I co-founded as its CTO, and independent consulting alongside all of it. Infrastructure has been part of the work from the start, from data centers and servers to infrastructure as code since 2016 and Kubernetes in production since 2017, on AWS, GCP, DigitalOcean, and self-managed clusters. I build and run my own products, including apps on iOS, Android, and the web that reached millions of users and held top-chart positions for more than four years, and the Visiting Objects platform, and now build AI-augmented workflows on top of all of it.
What that means for you: the person who reviews your architecture is the person who writes the report, does the work that follows, and knows the system when something goes wrong. No handoff to a delivery team you haven't met. I build with AI myself, every day, on the same engineering practices I will bring to your product.
22 years
In software engineering
16k+
GitHub contributions in the last year, many through my AI agent delivery system
VibeHospitalOnyx Edge's practice for AI-built productsActive since 2026
OnyxEdgeFounder and principal engineerActive since 2020
VisitingObjectsA product I built and operateActive since 2022
Message me on Upwork
Start with a checkup
The first read is free. No obligation, no jargon.
Message me on Upwork
Tell me what you built, where it runs, and what's on your mind.
I look at where it stands
A first read in reply, and whether an assessment fits.