<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: sm123</title><link>https://news.ycombinator.com/user?id=sm123</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 06 May 2026 23:34:59 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=sm123" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by sm123 in "Ask HN: Who is hiring? (April 2026)"]]></title><description><![CDATA[
<p>Founding Technical AE | <a href="https://build.io" rel="nofollow">https://build.io</a> | REMOTE (working hrs must overlap w/ N America) | Full-time<p>Build is a full-stack cloud platform — we own the stack from bare metal up. Our customers are engineering-led SaaS teams who've outgrown their current setup and want effortless deployment, real environments, and predictable pricing without the infrastructure overhead. Think teams escaping from Heroku, scaling past Vercel/Fly.io, or trying to escape AWS/GCP/Azure complexity.<p>We're hiring our first Technical Account Executive. This is a full-cycle role — you'll own outreach, discovery, and demos through to close, partnering closely with the VP Sales.<p>We're looking for someone with 4–7 years in devtools or cloud infra space who can hold a real conversation with engineers and understand what's actually broken in their setup. A background in cloud/devtools sales or Solutions Engineering but ready to own the whole cycle are both strong fits.<p>Apply: <a href="https://www.linkedin.com/jobs/view/4394700127/" rel="nofollow">https://www.linkedin.com/jobs/view/4394700127/</a> or email steven[at]build.io direct.</p>
]]></description><pubDate>Thu, 02 Apr 2026 16:51:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=47616922</link><dc:creator>sm123</dc:creator><comments>https://news.ycombinator.com/item?id=47616922</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47616922</guid></item><item><title><![CDATA[New comment by sm123 in "An Update on Heroku"]]></title><description><![CDATA[
<p>You’re right - reading that back, it comes across as a “no,” and that wasn’t my intent.<p>We should show pricing, and we will. We temporarily stripped the site back while overhauling positioning and pricing, which is why it’s missing right now. That’s on us, not a stance against transparency.<p>In the meantime, I’m more than happy to share pricing directly.<p>At a high level on our pricing:
- Current customers are on a mix of usage-based and fixed monthly plans, depending on their needs. We've found many of our customers love the fixed plan as it's a whole new level of predictability.
- We’re generally architected to land well below Heroku’s Enterprise pricing and to be competitive with a IaaS.
- We want pricing to get out of your way as you scale, so no big steps in pricing as you add services.
- Databases are HA by default and support replication.
- Pipelines and review apps don’t require hacks to avoid per-review-app database costs.<p>Happy to answer specifics here or over email if helpful.</p>
]]></description><pubDate>Sat, 07 Feb 2026 19:24:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=46926726</link><dc:creator>sm123</dc:creator><comments>https://news.ycombinator.com/item?id=46926726</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46926726</guid></item><item><title><![CDATA[New comment by sm123 in "An Update on Heroku"]]></title><description><![CDATA[
<p>llIIllIIllIIl & runako give me an email on steven[at]build.io and I'll share. As mentioned, we stripped the site back while we overhaul and we certainly didn't expect this today!</p>
]]></description><pubDate>Fri, 06 Feb 2026 22:37:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=46919099</link><dc:creator>sm123</dc:creator><comments>https://news.ycombinator.com/item?id=46919099</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46919099</guid></item><item><title><![CDATA[New comment by sm123 in "An Update on Heroku"]]></title><description><![CDATA[
<p>Couldn’t agree more. That “git push and you’re live” moment removed a huge amount of accidental complexity, and it’s been the guiding experience behind what we’re building at Build.io.</p>
]]></description><pubDate>Fri, 06 Feb 2026 17:27:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=46915625</link><dc:creator>sm123</dc:creator><comments>https://news.ycombinator.com/item?id=46915625</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46915625</guid></item><item><title><![CDATA[New comment by sm123 in "An Update on Heroku"]]></title><description><![CDATA[
<p>Build.io came out of this exact problem a few years ago (I joined in 25Q4) - trying to be what Heroku could have been if it had continued to evolve.<p>We offer the same default simplicity/speed, but with the ability to go deeper once teams hit scale, cost, or workflow limits. Plus a pricing model that stays understandable and improves as teams scale rather than punishing them for it.<p>Fair warning: the website is pretty light right now. It’s mostly a placeholder while we prep a broader push over the few months. Happy to answer questions here if helpful.</p>
]]></description><pubDate>Fri, 06 Feb 2026 17:20:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=46915521</link><dc:creator>sm123</dc:creator><comments>https://news.ycombinator.com/item?id=46915521</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46915521</guid></item></channel></rss>