Update post

LoreKeep private beta now runs on the live stack

LoreKeep is now running as a real deployed web app on Vercel with a Neon production database. This round also hardened the first private-beta path: Prisma migrations were applied to the live database, update and upcoming pages stopped depending on build-time database reads, and early production auth query overhead was reduced before broader tester onboarding begins.

Back to updates

Private betaLive2026-03-31 21:49 UTC

Post links

Keep browsing

Move between the update feed, upcoming work, and the editor from the same reading surface.

Open updates Open upcoming Back to home

What changed

A concise summary of the work delivered in this release.

Deployed the web app to Vercel Hobby and connected it to a Neon production database.
Applied the full Prisma migration history to production so the live app has the real schema instead of an empty database shell.
Removed build-time database dependence from the public updates and upcoming feeds so first deploys are safer on fresh environments.
Reduced current-user auth round trips so hosted requests do less redundant server-side database work.

User value

How this release improves the experience, workflow, or control users get from LoreKeep.

Private beta testing can now happen against a real hosted environment instead of only localhost.
The live app is less fragile during first deploys and fresh-environment setup.
Hosted performance now reflects real infrastructure tradeoffs, which makes future optimization work more honest and targeted.
This creates a clearer path to extension end-to-end testing against the real app URL.

Full notes

Additional context, implementation notes, or rollout details for this release.

LoreKeep has crossed the line from local-only development into a real private-beta environment. The deployed app now boots from a production database, the public updates and upcoming feeds no longer block the build when the database is empty, and the first pass of server-side auth query cleanup is in place to reduce extra round trips on hosted infrastructure.

This does not mean launch readiness is finished. The next work stays focused on the extension trust loop: detector cleanup, resume reliability, floating-button stability, and the overall save, update, and continue experience that needs to feel dependable before a broader beta or store submission.

Release status

Current state

A quick snapshot of how this update is categorized and published.