Justin Rhee retweeted
YC F26's @pomeradoai and co-founder @akshay_manglik uses Porter for scalable infra he doesn't have to manage, made SOC 2 compliant in one click.
Looking to deploy with your AWS/Azure/Google Cloud credits? Redeem the Porter startup deal: porter.run/startups/aws-azur…
Justin Rhee retweeted
YC F26's @lettercompany and founder @mathewpregasen leveraged Porter across both his YC startups for the cost savings scalability, and reliability benefits of AWS with the devex of a PaaS.
Use your AWS/Azure/Google Cloud credits with zero DevOps overhead: porter.run/startups/aws-azur…
Starting today, you can host sandboxes for running agents and untrusted code in your own AWS account.
Self-hosted sandboxes on Porter are now officially available for all users. Many companies from our YC-only beta including @atobHQ, @MaingenInc, and startups in the current batch like @lettercompany have been running production agents on Porter sandboxes for a few months now.
As with all of Porter's infra primitives, everything can be seamlessly run within your own AWS account (and using your existing cloud credits).
Justin Rhee retweeted
YC S26’s Petrarch and founder Sudhish Swain use Porter for the convenience of a PaaS in their own cloud.
Use your AWS/Azure/Google Cloud credits with zero DevOps overhead: porter.run/startups/aws-azur…
Justin Rhee retweeted
YC S26’s @getcontextdev and founder @mynameisyahia migrated to Porter so they don’t have to worry about DevOps during YC.
Use your AWS/Azure/Google Cloud credits without any infra headaches: porter.run/startups/aws-azur…
Justin Rhee retweeted
YC W26’s @endclosehq and founder @DavidNewell95 use Porter for the scalability and reliability of EKS with the convenience of a PaaS.
Looking to deploy with your AWS/Azure/Google Cloud credits? Redeem the Porter startup deal: porter.run/startups/aws-azur…
We've fully overhauled infrastructure audit logs on Porter. You can now query activity across any of your connected AWS/GCP/Azure cloud accounts.
As developers and agents are provision and mutate infrastructure at an unprecedented rate, having a queryable trail of activity is more critical than ever.
Full changelog: porter.run/changelog/api-aud…
Last week I spoke at @ycombinator DevTool Day. The focus of my talk was a summary of the merits and demerits of selling to startups.
A lot of people don't realize that in the beginning, Porter never intended to have startups as users. After years of pivoting we initially built a product designed to migrate Enterprise-tier PaaS users to the hyperscalers.
I remember actively turning away early-stage companies looking to use us because they seemed too small to justify the migration effort.
Eventually, a couple startups hell-bent on using us managed to self-serve even though we had no documentation and had exclusively built our "onboarding" flow as an internal tool to process white-glove migrations.
We let those startups stay on the platform expecting nothing to come of it.
Luckily for us, we had some rocket ships in that initial sample. A few of those users rapidly grew to a significant usage scale (with individual clusters on the order of terabytes of RAM and hundreds of nodes) within months of onboarding.
This was larger and higher-value than most of the customers we were running through a multi-month sales process. That got our attention.
Even still, we were initially pretty reluctant to bet the farm on startups. As any VC knows, all the growth is overwhelmingly concentrated into a tiny subset of companies.
This gets to a key downside of pursuing this strategy: unless you have a product that an overwhelming percentage of startups can use (like payment processing, HR, or corporate card), you run the risk of not capturing enough mindshare to effectively guarantee there are some winners in your basket.
If your carrying capacity for pre-seed startup adoption is something like 15% of all companies, you could struggle to get off the ground unless you're somehow indexing for only the best of the best.
For devtools in particular, you're almost always better off going truly bottoms-up with indie devs if your product allows it.
In retrospect, I believe we were fortunate that two things were the case: (1) frustration with DevOps overhead (i.e. having to manage AWS/GCP/Azure) is essentially ubiquitous, and (2) cloud infrastructure is a higher-order expense for virtually all startups (probably the 2nd or 3rd largest line item after payroll and tokens).
The upshot is also massive. Winning startup mindshare means you are building for the next generation of public companies.
If you can keep up with your best customers and preserve sufficient pricing power, you have the ultimate NRR engine.
As a devtool company, there's also nothing better than getting to work with smart, high-growth teams at the bleeding edge of technology.
I received a cease and desist for our company logo, so we turned it into an opportunity to rebrand.
A few months ago, I received an email from a large consumer company with a legal notice that our logos looked too similar.
They were generally civil but insisted that we discontinue the use of our existing logo.
In truth, this was mildly amusing to me given our logo's origin: a few years back during YC, I just typed "porter" in Figma using one of the default fonts (Montserrat).
It was never meant to be a real logo, but we figured it wouldn't make or break Porter.
Fast-forward to the present and I guess enough folks have heard about us for a large player in a different industry to care.
At the end of the day, what really matters as a devtool company is your product, but a brand can set the high-water mark that you aspire to with everything else you do.
We wanted the new identity to exemplify our more flat, graphic-leaning taste while featuring composable elements (or "atoms") that mirror how we think about compute.
In retrospect, I'm really glad this happened and served as a forcing function for refreshing our brand.
As with life so with startups: the journey is difficult either way, so you might as well make it count.
Working with Dalton since our YC journey has been incredibly helpful.
For any founders thinking about raising a Series A, I highly recommend checking out @Standard_Cap.
After raising a $20M Series A in 11 days, some founders have reached out asking, “Justin, how did you raise so quickly?”
The truth is, we weren't even looking to raise.
About a year and a half ago, David from FirstMark reached out. I'm someone who generally hates talking to investors, so my instinct was to ignore it.
But David kept showing up. Instead of sending generic "let's get coffee" messages, he invited me to in-person events where I could meet people doing interesting work.
Through FirstMark's programming, I got to chat with the CTO of Duolingo, the founder of DataDog, and countless others. It was mindblowing how much David pushed us forward.
And at that point, I wasn't even in FirstMark’s portfolio yet. They were just going out on a limb to build trust.
Fast forward to last fall, and we were hiring a lot against revenue growth. We didn't need the money. But the relationship with FirstMark had gotten so strong that when David leaned in, we decided to run a lightweight process.
The timeline:
1. Told David we'd consider raising
2. Pitched the partnership a few days later
3. Signed the term sheet within 10 days
What made it fast wasn't some secret fundraising hack; it was a year of relationship-building that happened before we ever decided to raise.
Whenever another investor came with a term sheet, FirstMark just kept matching or beating. They’d already done the work to understand our business, developed conviction, and were leaning in hard.
So, it is possible to raise a Series A in 11 days..
...if you've spent a long time building relationships with people who you know, believe, and trust.
Speed in fundraising isn't about cramming the process or doing crazy FOMO.
It's about doing the real work slowly so the last part's fast.










