Skip to main content

Local-first architecture

Feature Request

I’m considering switching to Locu as my primary productivity platform, and I have a few questions regarding what you mean by “lifetime“ support.

On the pricing page, you state: “Pay once, use forever.”
Could you clarify what this means in practice?

My main concern isn’t lifetime updates - I’d be happy to pay for continued development if needed. Rather, I’m thinking about long-term access and usability. For example, will I still be able to use the app one, five, or even ten years from now?

More specifically:

  • Would the app continue to function if Locu as a company no longer existed?

  • Is Locu designed with a local-first architecture?

  • In line with local-first principles, would the app remain usable indefinitely without official hosting or an internet connection (excluding data synchronization, of course)?

Understanding this would help me assess whether Locu is a viable long-term platform for my workflow.

Posted by Ivan Harašta ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Locu

    Team•

    Jan 22

    Thanks for asking - these are fair questions.

    We're offline-first - your data is stored on your device, you can work without an internet connection, and everything syncs when you're back online. We use a server for syncing because we want to support real-time sync across devices (desktop, web, and mobile is in progress).

    If we ever stopped developing Locu (not on our radar), the infrastructure is built in a way that could switch to local-only sync. It's not our current priority, but it's technically possible (while integrations will not work). And of course, you'd always have the option to export all your data in case of acquisition of service shut down.

    "Pay once, use forever" means exactly that - as long as Locu operates, you have access. We're building this for the long term, and keeping users' trust is core to that.