Beyond that, agree it seems like it can just be anything in virtually any title

All this blog post can do is make people nervous and lead to customers moving elsewhere. Revenue will drop, and further compound their desire to not invest in the platform. What's the benefit/upside in publishing such an article?

All unlimited liability insurance companies (e.g. motor insurers in the UK) have reinsurance to take the hit on claims over a certain level - e.g. 100k, 1m etc.

For extreme black swan risks, this is how you prevent the insurance company just going bankrupt.

Reinsurers themselves then also have their own reinsurance, and so on. The interesting thing is that you then have to keep track of the chain of reinsurers to make sure they don't turn out to be insuring themselves in a big loop. A "retrocession spiral" could take out many of the companies involved at the same time, e.g. the LMX spiral.

It is common for founding engineers to start with a preexisting way of working that they import from their previous more-scaled company, and that approach is refined and compounded over time

It does mean starting with more than is necessary at the start, but that doesn't mean it has to be particularly complex. It means you start with heaps of already-solved problems that you simply never have to deal with, allowing focus on the product goals and deep technical investments that need to be specific to the new company

The reason is because the insurance companies want you to care about the car as an asset, on the basis that statistically they are driven more carefully (and therefore cause less third party property damage, bodily injury, etc.)

---

We hope this message finds you well. We're writing to share some important news about Humanloop's future and what it means for you as a valued member of our community.

Our news

We're pleased to announce that Humanloop has entered into a process to be acquired. However, as part of this process, we’ve made the very difficult decision to sunset the current Humanloop platform. We’re planning the sunset for September 8th, 2025—after this date our UI and API will no longer be available. Although the acquisition is yet to be formally announced, we’re reaching out now to give you as much notice as possible and minimise disruption.

You have been an integral part of our journey and we acknowledge that this news may come as a surprise and will likely disrupt your current projects and workflows that use Humanloop. We're committed to supporting you through this transition period as best we can.

Exporting your data

We want to ensure you have full access to your data, so we've prepared some tooling to help you export your data easily via our existing API endpoints. For organizations with extremely high log volumes, we can explore working with you on a tailored export solution. Soon after we sunset the platform, all customer data will be removed from our servers and backups—please begin migrating your data as soon as possible.

Our team will remain available through to September 8th to assist with data export and answer any questions about alternative solutions.

Thank you

Thank you for being such an important part of the Humanloop story. We're extremely grateful for the trust you've placed in us and are incredibly proud of what we’ve built with your support. Together, we’ve helped define industry standards for this new AI tooling layer of prompt management, evaluations and observability. Your feedback, collaboration and support have been a cornerstone for everything we've built and accomplished.

We're committed to making this transition as smooth as possible, so please don't hesitate to reach out for help. We’re excited to share more details soon about what’s next for us and what it means for the future of our mission.

Sincerely,

The Humanloop Team

Comments URL: https://news.ycombinator.com/item?id=44592216

Points: 12

# Comments: 6

If you don't qualify as a "reader" app, what you're suggesting actually isn't allowed - you're _required_ to offer IAP if you provide access to the service in-app

3.1.3(b) - "may allow users to access content [...] provided those items are also available as in-app purchases within the app"

https://developer.apple.com/app-store/review/guidelines/#oth...

The app I work on is a content app, but they decided it did not qualify as a "reader" app because we had polls alongside the content, which were interactive and therefore excluded us from the definition.