Top all-time · #5303
Stedi
Company blog · stedi.com/blogprogrammingbusiness
Stedi is the company blog at stedi.com, writing about programming and business. Since 2017, 14 different Hacker News readers have linked it 47 times, most often “Excerpts from the Annual Letter”. It is still writing: the last post was on 2026-10-30, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN commenters mention Stedi mainly as a company and product: one links the founder's personal writing, and another credits its tool for turning EDI data into JSON. The comments do not judge the blog's writing.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Stedi is the only headless healthcare clearinghouse and RCM engine. We offer modern, AI-ready APIs for eligibility checks, claims, transaction enrollment, and more.
Most-linked posts?
- Excerpts from the Annual Letter4 people · 5 mentions · first linked 2022-05-24
- We discovered an AWS access vulnerability4 people · 4 mentions · first linked 2024-04-10
- What makes EDI so hard?3 people · 3 mentions · first linked 2022-01-06
- The unwritten laws of engineering at Stedi2 people · 2 mentions · first linked 2024-04-11
What Hacker News says?
Stedi | Serverless Engineer | Full time | Remote / fully-distributed Stedi is working in one of the biggest markets on the planet – EDI, the technological backbone of the physical product economy. We’re building a next-generation platform: a ubiquitous commercial trading network to automate the trillions of dollars in B2B transactions exchanged by nearly every company on Earth. We are a 25-person, fully-distributed…
Comment linking /careers
on “Ask HN: Who is hiring? (August 2020)”Submitted What makes EDI so hard? as a story · 81 points
HN discussionStedi | http://www.stedi.com | Boulder, CO | Onsite | Senior backend engineer We're a three-person startup and we've raised $3.7 million in seed funding from First Round Capital, Bloomberg BETA, and other top investors - we're building a modern EDI platform to automate billions of dollars in transactions between retailers like Amazon and Wal-Mart and suppliers like Fitbit and Eero. If you aren't familiar with EDI, i…
Comment linking /
on “Ask HN: Who is hiring? (September 2017)”Submitted The unwritten laws of engineering at Stedi as a story · 53 points
HN discussionThat's him. Though he doesn't seem to have updated his personal website, he's now CEO/Founder of Stedi: http://www.stedi.com/
Comment linking /
on “You are not 'behind'”Submitted Serverless SFTP and infinitely-scalable data storage as a story · 25 points
HN discussionGood overview. I wrote about this in a bit more detail on our blog recently: https://www.stedi.com/blog/what-makes-edi-so-hard
Comment linking /blog/what-makes-edi-so-hard
on “Why isn't there a universal data format for résumés?”Submitted Translate Between JSON and EDI as a story · 22 points
HN discussionKnew I recognized some of this writing before. This book is quoted in an annual letter[0] from Zack Kanter which is also worth a read: > Eliminating toil allows people to focus on the inherent complexity of the difficult, interesting problems at hand, rather than the incidental complexity caused by choices made along the way. > Toil can be eliminated...by drawing the system boundary a bit differently. When we use an…
Comment linking /blog/excerpts-from-the-annual-letter
on “Eliminating Toil”Submitted Postman is probably not HIPAA-compliant as a story · 14 points
HN discussionWe are launching drop-in replacements for their APIs: https://www.stedi.com/blog/replacements-for-change-healthcar...
Comment linking /blog/replacements-for-change-healthcare-apis
on “US prescription market hamstrung for 9 days (so far) by ransomware attack”Submitted What makes EDI so hard? as a story · 13 points
HN discussionHi all: I'm the founder/CEO of Stedi. Came here to say that we're preparing to publicly launch drop-in replacements for Change's Claims and Eligibility APIs[1]. Our new API will allow customers who have been using Change to directly switch with minimal development effort. The API: i) accepts Change JSON request format, ii) translates it to X12 270/837, iii) submits it to a clearinghouse (we have a master connection…
Comment linking /docs/api-reference/post-healthcare-eligibility
on “US prescription market hamstrung for 9 days (so far) by ransomware attack”Submitted Excerpts from the Annual Letter as a story · 8 points
HN discussion> I get the impression they would be perfectly happy shipping nothing for long periods. I wouldn't say _happy_, but we were certainly _willing_ to do this for long periods of time to get the right foundation built (for reference, we built for 5 years before launching). This is made explicit in the opening: > As a result of following the framework, product development may sometimes come to a screeching halt. The work…
Comment linking /blog/excerpts-from-the-annual-letter
on “The unwritten laws of engineering at Stedi”Submitted We discovered an AWS access vulnerability as a story · 7 points
HN discussionYep, there's no way around mapping – the data has to get mapped somehow. The 835/837 are a bear. You can save some time if someone has built a mapping template already – say, from a transaction type in Oracle to the 837 – but if it's a custom system you're mapping to/from (like a homegrown API), it's impossible for a template to exist...it has to be done from scratch. We've found that many of the fields end up being…
Comment linking /products/mappings
on “Translate Between JSON and EDI”Submitted Getting started with the X12 file format as a story · 7 points
HN discussionA success I've had is building datasets from the electronic data interchange (EDI) transmissions we receive. EDI is an old standard, and everyone implements it slightly differently, but Stedi ( https://www.stedi.com ) has made it simple for me to turn EDI into JSON. Like you said though, there are still folks using paper receipts/PDFs.
Comment linking /
on “Ask HN: Working with CPG Retail Data”Submitted Date and Time in EDI (Electronic Data Interchange) as a story · 7 points
HN discussionFull paper: https://www.stedi.com/documents/papers/how-stedi-uses-automa...
Comment linking /documents/papers/how-stedi-uses-automated-reasoning-for-access-control-policy-verification.pdf
on “How Stedi uses automated reasoning for access control policy verification”Submitted We discovered an AWS access vulnerability as a story · 5 points
HN discussionSubmitted Using Stedi for AI voice agent workflows as a story · 3 points
HN discussionSubmitted We discovered an AWS access vulnerability as a story · 3 points
HN discussionSubmitted The unwritten laws of engineering at Stedi as a story · 3 points
HN discussionSubmitted Vulnerability in AWS STS as a story · 2 points
HN discussionSubmitted Stedi EDI Catalog as a story · 2 points
HN discussionSubmitted Public Guides: next-generation EDI implementation guides as a story · 2 points
HN discussionSubmitted Control Numbers in X12 EDI as a story · 2 points
HN discussionSubmitted Stedi Mappings as a story · 2 points
HN discussion