CaseMark tightens up its signup form

A small auth hotfix on kveton's fork hints at a bigger story about CaseMark running its own login stack.

intakeinfrastructure

The signup form on CaseMark's fork was telling users one thing while the backend enforced another. Password rules on the page didn't match what the server actually accepted, so anyone who slipped through the cracks got a generic failure instead of being told what was wrong. kveton landed a same-day fix that aligns the form's rules and copy with the real policy and pipes the backend's actual error messages through to the screen.

The more interesting signal is underneath. CaseMark is now running its own authentication layer - Better Auth, an open-source login toolkit - wired into a custom signup UI. That's a deliberate move away from leaning on a hosted identity provider, and it means small mismatches between the two halves become user-visible bugs the team has to chase.

So what Anyone evaluating CaseMark as a buildable legal-AI platform should note it's investing in owning its own auth stack rather than renting one.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
b074eeb6 Fix signup password validation kveton 2026-05-04 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-287.md from inside the repo you want the changes in.

⬇ Download capture-thread-287.md