Casengine is a bilingual (Arabic/English) legal practice management platform marketed as ‘#1 Legal Practice Management Software in UAE.’ Developed by Code Engines Software LLC (Codengines), headquartered in Dubai. Features include case management, payment scheduling, time/expense tracking, deadline monitoring, task automation, lead management, and real-time case updates. Available on iOS. Reported USD $28M valuation with equity investment from Dubai Cultiv8 and a UAE Royal Family office (per F6S profile of former executive). Co-founder/CEO: Pravesh Kumar. 11-50 employees per LinkedIn. Active on social media through February 2026 (LinkedIn commentary on legal industry trends). Listed on Capterra (1 review, 4/5), GetApp (1 review, 4/5), TrustRadius alternatives page. All-inclusive pricing model (no tiers, no hidden costs). Primarily serves UAE and Middle Eastern law firms. Instagram active with marketing about pricing transparency. Reddit presence limited to self-promotional posts only.
Company Info
- Sector: Legal Tech
What We Haven’t Verified
This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.
Workflows
Based on practitioner evidence, Casengine App is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Casengine App addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
Client calls asking 'what's happening with my case?' — paralegal has to interrupt the attorney because matter status lives in someone's head, not a system
Solo attorney paying $500+/month across 6 different software tools that don't share data — needs one system that actually handles the basics without nickel-and-diming
Firm uses separate tools for intake, documents, billing, and e-signatures that don't talk to each other — opening a new matter means entering the same client info 4 times across systems that should but don't share data
Where it fits in your workflow
Community Data
Loading practitioner-sourced data…