Porter

Heroku runs on AWS. Vercel runs on AWS. Render runs on AWS. Everything is an AWS wrapper. So you might as well deploy to your own AWS account and use your cloud credits. porter.run/for-seed-stage…

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-a…

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-a…

YC W26’s @usepolymorphs and founder Andrew Sy rely on Porter to stay focused on shipping product instead of managing infra. Check out the easiest way to use your AWS/Azure/Google Cloud credits: porter.run/startups/aws-a…

Here's the full changelog: porter.run/changelog/api-…

API Audit Logs 2.0: A queryable record of all project-wide activity against the Porter API (including from the dashboard). CLI and Browser Session Management: The Porter CLI now authenticates with short-lived sessions. All active browser/CLI sessions can be monitored and revoked. Short-lived Cloud Credentials: Porter now accesses your cloud through session-based, auto-expiring tokens instead of long-lived access keys. Secure Cloud Access for Workloads: Your applications can now receive scoped cloud permissions natively, with no persistent access keys to provision or rotate.

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.

YC P26’s @trymemoir_ai and co-founder @ZhanJason179 chose Porter for production-ready infra without any DevOps overhead. Looking to deploy with your AWS/Azure/Google Cloud credits? Redeem the Porter startup deal: porter.run/startups/aws-a…

YC P26’s @ontoratech and founder @dav1dk0rn rely on Porter to seamlessly leverage their AWS/Azure/Google Cloud credits. Check out the easiest way to deploy to your own cloud: porter.run/startups/aws-a…

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-a…

@deploy_mom You can reach us at billing@porter.run.

@porterdotrun could you please share the best email for accounts management & billing support?

YC W26's @robby_assistant and co-founder @FerozeMohideen leverage Porter for automated infrastructure management so they can focus on shipping product. Redeem our startup deal and deploy effortlessly with your AWS/Azure/Google Cloud credits: porter.run/startups/aws-a…

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.

Last week I had the pleasure of interviewing my YC Group Partner @daltonc at the @brexHQ office. Here was my biggest takeaway from our fireside:

Opalite Health (YC W26) co-founder and CTO @akmehregan uses Porter to ship product for enterprise customers without DevOps overhead. Looking to deploy with your AWS/Azure/Google Cloud credits? Redeem the Porter startup deal: porter.run/for-seed-stage…

YC F25's @usecrunched chose Porter for the reliability and scalability of EKS with the simplicity of a PaaS. Looking to deploy with your AWS/Azure/Google Cloud credits? Redeem the Porter startup deal: porter.run/for-seed-stage…

There are only 2 types of founder advice here on X/Twitter. One is valuable. The other is almost worthless. Here's how to tell the difference: Let me say this out loud: I deeply discount founder advice. Yes, I'm fully aware of the irony of saying that as a founder who (sometimes) shares advice on X. Here's why I feel this way: for every founder who made it and is now dispensing wisdom from a position of success, there is a long tail of people who said the exact same things, followed the exact same playbook, and crashed. The advice was identical. The outcome was completely different. And even the founders who are currently winning, who knows where their companies will be in five years - there's so much luck involved, so much random chance, so many invisible variables that the signal-to-noise ratio on most prescriptive founder advice is extremely low. But I think there's a nuance here that matters quite a bit, and it's the thing I'd want any early-stage founder to internalize: Put all founder advice into two buckets before you decide how much weight to give it. Bucket 1: "Here's what I actually did." This is a founder telling you the specific story of how they handled a real situation. What they tried, what worked, what didn't. That's a genuine data point. You can collect those from many founders, aggregate them yourself, and draw your own conclusions. That has real value. Bucket 2: "Here's what you should do." This is a founder projecting their experience onto your situation and telling you the right answer. What they'd do in your shoes. How they'd solve your specific problem. This is shaped by survivorship bias, by luck, by a thousand variables they don't understand about your context. Heavily, heavily discount this. The distinction seems small but it's everything. Counterfactuals like “what I would have done differently” and “what I think you should do” are almost worthless because they're untested hypotheticals dressed up as wisdom. I try to stay in Bucket 1. You should hold me to that.