Sabitlenmiş Tweet
Today I'm excited to share that Nuon is officially open source!
You can read more about our announcement here: nuon.co/blog/oss-annou…
English
Jon Morehouse
4.5K posts
Jon Morehouse
@nuonjon
The BYOC guy. Founder and CEO @nuoninc. Learn how to unlock enterprise customers. San Francisco.
your customer's cloud account Katılım Ekim 2011
707 Takip Edilen960 Takipçiler
@jamesperkins I got my hands on some of the Diet Coke with limes a few months back.
One of my all time favorites. Up there with the one on the left.
English
@utpalnadiger Absolutely
Rather a 3 plate squat than most any other lift.
English
If the founder doesn’t have at least one lift with 3 plates, NGMI
English
One of the best things we did early on at Nuon was build our control-plane using "the uber go stack".
temporal, fx, zap.
We recently wrote about how we use fx + fxtest for integration style testing of our api.
English
Just as important to make your content accessible to agents, as your product.
English
@travers00 @p0 We're based right here in South Park, too! Best part of the city for startups
English
.@p0 just opened our first official San Francisco office in the heart of South Park
our team is growing rapidly and expanding our footprint in both SF + Palo Alto
we're looking for builders across all roles: gtm, engineering, deployed eng, research, etc. - DM me!
English
We've long held conviction that BYOC is not just handing your customer a Helm chart.
Sure, Kubernetes, Helm are standards at this point for customer deployments.
Sure, you can package your app (and some dependencies) with Helm.
But that's not BYOC...
Bring Your Own Cloud is about offering a SaaS, directly in your customer's account.
Your customer has control, but you are responsible for making sure things work.
All while making it secure.
Today, we're announcing bringyourhelm.com - anyone with a Helm chart can connect their chart, configure customer inputs and create a BYOC app in minutes.
This takes your helm chart and gives you:
1. A single installation for any customer environment.
2. Ability to push updates, watch for issues, and mitigate them when they come up.
3. Dynamic permissions, policy enforcement, break-glass and all the auditability you need to meet customer security demands.
Once you are done, you can hand your customer a nice installation portal, empower your CS team to setup customers faster and actually deliver on the SaaS part of BYOC.
Read more on our blog - nuon.co/blog/bring-you…
English
@leerob Amazing been wanting this for a while
I forked avante a while back, and have been making it work with ACP better (uses rust acp bindings and some other things in there).
Trying out today!
English
You can now use Cursor with 30+ ACP clients, including OpenClaw 🦞
This means complete access to Composer 1.5, codebase indexing and semantic search, and more!
Here's an example with avante.nvim
English
One thing I've learned about BYOC, time and time again.
No matter how much you try to "simplify" your application, when it comes to running in production, you are going to have more requirements than you think.
Even the simplest, single-helm chart apps we've seen, end up with 5 or so additional pieces deployed.
English
You can tell a lot about a team based on the keyboards they use.
We wrote about ours here: nuon.co/blog/nuon-keyb…
Sam Lambert@samlambert
The PlanetScale office has a keyboard library so people can try and enjoy various keyboards.
English
@samlambert The kinesis is the real one here.
I added a solenoid to mine, and it sounds as good as it looks.
English
The PlanetScale office has a keyboard library so people can try and enjoy various keyboards.
English
So happy for this one.
Justin was an early supporter and trial user of Nuon. Amazing technologist, and great to work with.
Love to see it, and congrats 🚀
Justin Torre@justinstorre
Hi friends! Big news today: Helicone is joining Mintlify 🚀 3 years ago, we started Helicone out of YC W23 with a simple bet: every hype-cycle has a massive observability market, and we felt like AI was going to be even more prevalent. We knew someone needed to build the platform to ingest and make sense of it all. So we did. Years of grinding and a handful of pivots later, we built something real that customers use every single day. I spent most of that time worried about tomorrow and never really stopped to look back. But looking back now: - 14T+ tokens processed - 30k+ sign ups - 36M+ users tracked - Trending on Github last year (5.2k stars) - $1M+ ARR - Product of the week on Product Hunt That still blows my mind. So why Mintlify? In a post-AGI world, a knowledge infrastructure layer is the thing that makes the most sense for companies to invest in. Waymo didn't reinvent the roads, but still needed to learn about them. Mintlify is the information layer for agents building the systems of the future. The overlap with what we were building at Helicone was obvious. Same world, different angle. More importantly, I actually like the team and the product. That sounds simple but after talking to a dozen companies, it's rarer than you'd think. @handotdev and @hahnbeelee are both incredible and formidable founders that Cole and I really admire. Things I learned building Helicone that I think are underrated - A 5-person team can do an absurd amount if everyone is locked in. Headcount is not a moat. - If you have data at scale and need analytics, just pick ClickHouse. Don't overthink it. - The grind is real, and it's fun. But REALLY try not to be stressed when you aren't grinding. That part took me way too long to learn. - It's never too late to pivot and try new things. - Charge more for your product. What's next I'm going to be leading an engineering team at Mintlify and I'm genuinely excited about what we're building. Keep an eye on my X, because I can't wait to be tweeting about it more. Thanks to @coleywoleyyy for being an incredible co-founder. Thanks to our team, our investors, our customers, and everyone who bet on us early. And thanks to my fiancee for putting up with the chaos of startup life. That part is deeply underappreciated. And lastly, thank you @mintlify for taking a bet on the Helicone team. We are so excited for the next phase. More to come. DMs are open.
English
@jonathangrahl @themandeepc Policy tools like kyverno etc can take you a lot further than you'd expect here, as well.
English
@themandeepc Yes, we always worry about this! It takes significant effort to reach a good state of isolation for untrusted workloads.
Gvisor helps a lot with this. Still risk of human error for e.g. shared credentials
English
I just ran a load test of starting a million sandboxes on our sandbox infra. Managed without any hiccups!
We've been tuning them for a while and are now able to support multiple 10x growths this year without rearchitecting.
GKE is truly impressive!
English
@jonathangrahl We've found that spinning up GKE clusters take about 50% less time than anything with EKS.
Are you using managed node pools, or auto-pilot?
English
We've learned a lot about BYOC over the years.
It's not just, deploy your app in a customer's environment and go.
@sharkymark123 broke down why that is just the beginning of the journey.
Mark Milligan@sharkymark123
English
@ovaistariq Is there anything better as an infra founder than launching a new version of your cli?
English
We care a lot about DX at Tigris. That’s why we invested in our own native CLI, even though Tigris works great with the AWS CLI (and still does).
Because CLI is the first touchpoint with any dev product.
Today’s upgrade: we moved the Tigris CLI to Bun: tigrisdata.com/blog/using-bun…
English
We're gonna look back in 2/3 years and reminisce on the time we used agents via CLIs.
Part of why I'm so excited by ACP is it's what enables us to get closer to actual agent-development-experiences
Feel like the folks at @AmpCode are cooking up something next level here
English