Inrupt.net Service Migration Announcement

1

Read the full announcement on Inrupt’s Blog

Inrupt has been running inrupt.net for a number of years. In our ongoing commitment to provide secure and reliable services, we’re announcing the retirement of inrupt.net, which has been running on an early prototype implementation of a Solid server.

Effective March 31st, 2025 10:00UTC, inrupt.net will be shut down and discontinued. We’re excited to direct you to our free Developer Preview offering, PodSpaces, which runs on Inrupt’s Enterprise Solid Server.

Inrupt will perform a migration of inrupt.net accounts to PodSpaces. Please read more at our blog post on account migration details.

We appreciate your understanding as we make this necessary transition to provide a more robust and secure service.

4 Likes
2

Thanks for the heads-up Kyra! The blog post says:

Only inrupt.net accounts that meet these requirements will be migrated:

  • The Pod has an associated email address
  • You’ve uploaded resources to your Pod, or modified default resources in the Pod two or more days after the Pod was created

It’s not clear to me how to associate an email address with a Pod? Or even how to check that one is associated with it already?

1 Like
3

Hi @Vincent! We are investigating the easiest way to determine this. I’ll post an update here once we have an answer. Thanks!

2 Likes
4

The only valid email is the one located in the podRoot/.acl.
This is the one used to send restore password or delete pod emails.

  • the restore password link is https://inrupt.net/password/reset
  • the delete account link is https://inrupt.net/account/delete
    To send the delete email you must be logged in and either :
    • type the delete pod link in your browser or
    • go to the bottom of the preferences tab

If anyone need to change it, you can edit the email address in the browser by being logged in and going to your pod root ACL https://YourPodName.inrupt.net/.acl and use the edit-pane.

3 Likes
5

– mood post –

I think it is bad News from Inrupt.
There has been no prior discussion with the Community, may be with ODI ?
Transparency is a MUST to confidence when working with a Community !!!

Inrupt could have supported a longer term involvement, but I suppose this is not anymore in the business plan OK, but not even in their image plan.

It is a sign that your data were not really yours,
all links to your pod will be lost,
all the apps that where working on your data will not work anymore.
PodSpaces is not compatible.

With a better involvement there could have been a least some discussion about a migration to CSS or PIVOT.
Never use a company domain name. They will not transfer it.
The Inrupt involvement and support to the Community is neering zero.

Fair for Inrupt, it was stated on the https://inrupt.net root page

If you want to recover your data ask Inrupt.
They may give you a zip file with the help of European RGPD.

1 Like