The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Day 34 of building DocuPulse AI.
Today's problem is the one that would actually get a company sued.
DocuPulse analyzes confidential contracts. The moment two law firms use it, a hard rule kicks in: Firm A must never, ever see Firm B's data. Not their contracts, not their answers, not even a cached response.
That last one is the trap. Yesterday I built a cache that matches questions by meaning. So picture it: Firm A asks "what's our liability cap?" and the answer gets cached. Firm B asks the same question about their contract. A naive cache sees two near-identical questions and serves Firm A's confidential answer to Firm B. No error. No warning. Firm B just reads another company's private contract terms, presented as their own.
That's not a bug. That's a confidentiality breach between two clients — the kind that ends a legal-tech company.
The fix is old-fashioned backend discipline: every single query — every document search, every cache lookup, every stored result — is filtered by which customer is asking, before anything else runs. I made the customer ID a required parameter on the search functions, so there's no way to accidentally run an unscoped query. The safe path is the only path.
The AI made this trickier only because the dangerous queries — semantic search, meaning-based caching — don't look like normal database queries. So they're the easy ones to forget to protect. And a forgotten filter here doesn't crash. It quietly hands one client another's secrets.
The pattern of this whole month, at its highest stakes: the failures that matter most are the silent ones.
#AIEngineering #Laravel #BackendEngineering #BuildInPublic
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
Claude
Claude has entered the design space. How are you using it?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
Brand Design
The best brand designers are on Contra. Scroll to see what's trending in brand design. What are you building?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?
Related posts
Recently delivered a healthcare mobile app focused on improving user experience and operational workflows.
Using our SaaS boilerplate, SaaStacKit, we accelerated backend development and spent more time building the features that create real value for healthcare teams and patients.
Build faster. Focus on the product.
I've continued looking at accounting firm websites, and one thing keeps standing out.
A lot of firms explain what they do, but not who it's for. As someone visiting the website for the first time, it's surprisingly hard to tell whether the firm works with small businesses, startups, contractors, or larger companies.
I think that's a missed opportunity. People usually come to an accounting firm's website because they already have a specific problem. They want to know if the firm understands businesses like theirs.
A list of services doesn't answer that on its own. Context does.
The more websites I look at, the more I realize that good design isn't about making accounting look more exciting. It's about making expertise easier to understand.
.
.
.
Prokhorov®
helloprokhorov.com
Contra → contra.com/helloprokhorov
Man this looks really nice and fresh.
Your API works… but your app still feels slow? 🚨
Sometimes the problem isn't your frontend. It could be the way your backend handles requests.
A few things I always check:
⚡ Slow database queries
🔄 Too many unnecessary API calls
📦 Large API responses
🗄️ Missing database indexes
🔐 Authentication running on every request
Small backend improvements can make a big difference to the user experience.
What’s one performance issue you've struggled with in your project? 👇
cool!!!