Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Openfront Law Firm

openship.org

  • Free plan
  • Open source
  • Web
  • API
  • Self-hosted
8.0 Club score Visit openship.org

What Openfront Law Firm is

Openfront Law Firm is an open-source application for coordinating legal-practice operations, including intake, conflicts, matters, documents, billing, trust records, client sharing, retention and controlled agent work. Its workflows organize matter teams, courts and deadlines, communications, time and expenses, invoicing, trust ledgers and client sharing. Access controls include firm memberships and roles, matter-team assignments, ethical walls and precise resource grants for portal access. Records such as invoice lines, document versions, trust entries, signature events and audit events use append-only records or compensating operations. Integration features include encrypted credential records, external record links, communication and webhook records, API-key authentication, and OAuth authorization using S256 PKCE. These integration boundaries do not themselves send real email or SMS, store real documents, collect payments, calculate court deadlines, submit court filings or obtain signatures. The current source also lacks public intake and a client-facing portal interface. Deployment uses Node.js, Next.js, Keystone, Prisma and PostgreSQL; production requires explicit public and internal HTTPS origins. The general pricing page does not give a price specifically for Openfront Law Firm.

Who it suits

The maker describes it for law firms and legal operations teams seeking connected matter workflows, financial records, client collaboration and document history in infrastructure they choose. It requires technical deployment and additional operational preparation for real firm data.

Good to know, and what to watch

  • Open-source application with full source access on the free plan.
  • Includes matter roles, team assignments and ethical walls.
  • Maintains history for documents, trust entries and audit events.
  • Supports API-key authentication and OAuth authorization.
  • Provides matter task management and audit logs.
  • Current source has no public intake or client portal UI.
  • Integrations do not themselves send real messages or collect payments.
  • Real-data deployment needs reviewed operational and security procedures.
  • No product-specific price is stated on the general pricing page.

Free

Free

Starter

$49/mo

Professional

$199/mo

Enterprise

$399/mo

Free plan

Getting started

  1. Open the Openfront Law Firm website
  2. Choose the self-deploy Free plan or a listed paid plan
  3. Prepare Node.js, Next.js, Keystone, Prisma, and PostgreSQL
  4. Set explicit public and internal HTTPS origins for production
  5. Create a reviewed migration and restore procedure for real firm data
  6. Configure managed secrets, encryption keys, monitoring, and provider adapters

Limits to check

The Free plan is self-deploy and includes community support. Production use with real firm data requires migration and restore procedures, managed secrets and encryption keys, tested provider adapters, monitoring, incident response, and jurisdiction-specific legal review.

The Club's review

Overview

Openfront Law Firm is an open-source system for coordinating legal practice operations, from intake and conflicts to matter, billing, trust and document records. It is best suited to firms with technical staff prepared to deploy and maintain their own infrastructure. Its broad workflow scope and fine-grained access model are useful, but firms should not treat it as a finished client-facing platform or a compliance guarantee.

The application is intended for firms and legal operations teams that want connected matter work, financial records, client collaboration and integration controls in infrastructure they choose. That flexibility shifts substantial deployment and ongoing operational responsibility to the firm.

Key features

Connected matter work and record history

Openfront covers intake and conflict review, matter teams, courts and deadlines, communications, time and expenses, invoicing, trust ledgers and client sharing. Bringing those functions into one operational framework may help teams coordinate related work, though breadth alone does not replace the external services needed to carry it out.

Access combines firm memberships and roles with matter team assignments, ethical walls and precise matter- and resource-level portal grants. For firms that need to separate sensitive work, this layered approach is a meaningful control. Append-only records or compensating operations retain history for invoice lines, document versions, trust entries, signature events and audit events, supporting traceability without proving that a firm meets its accounting, retention or other obligations.

Integration boundaries and security

The system supports provider connection records, encrypted credential envelopes, external record links, communication delivery and webhook records, API-key authentication, and OAuth authorization code with S256 PKCE. Documented security controls include fail-closed authorization, keeping credentials out of GraphQL reads, bounded requests, disabled HTTP introspection and exact-resource portal shares. These are useful design safeguards for a system handling sensitive records.

Those integration records do not themselves send real email or SMS, store real documents, collect payments, calculate court deadlines, submit filings or obtain signatures. The current source also lacks a public intake flow and client-facing portal interface. Firms needing those services or interfaces out of the box will need other tools or additional implementation work.

The maker cautions that Openfront does not guarantee legal-ethics, privilege, trust-accounting, privacy, retention, signature, security or jurisdiction-specific compliance. A production deployment for real firm data also calls for a reviewed migration and restore procedure, managed secrets and encryption keys, tested provider adapters, monitoring, incident response and jurisdiction-specific legal review. This is a substantial burden, and a poor fit for a firm seeking a turnkey hosted service.

Pricing

Openfront Law Firm uses a freemium model, but the general Openfront pricing page asks visitors to choose a platform and does not give this product its own price. The general plans are therefore not a confirmed Law Firm quote; firms should expect custom pricing for the product unless they choose the self-deployed free option.

PlanPriceWhat it includes and who it suits
FreeFreeSelf-deployment, full source code access and community support. This is the practical starting point for technically capable firms willing to manage their own hosting and operations.
Starter$49 a month, billed monthlyUp to 500 orders per month, 1,000 products and 1 region. These commerce-oriented limits do not describe legal matter capacity, so firms should not assume this is a Law Firm subscription.
Professional$199 a month, billed monthlyUp to 5,000 orders per month, 10,000 products and 5 regions. Like Starter, its published quotas are not law-firm usage limits.
Enterprise$399 a month; billed Contact Us.Unlimited orders, products and regions. Its terms still describe general Openfront plans, not confirmed Law Firm entitlements.

The general paid plans use order, product and region caps, while the free option is explicitly self-deployed and comes with community support. No trial length, seat allowance or legal-specific quota is given for Openfront Law Firm, so firms should resolve scope and commercial terms before relying on a paid plan.

Platforms

Openfront Law Firm is available as a web application, API and self-hosted deployment. Its documented stack uses Node.js, Next.js, Keystone, Prisma and PostgreSQL; production requires explicit public and internal HTTPS origins. The self-hosting option gives firms infrastructure choice, but also makes deployment security, recovery and maintenance their responsibility.

Who it's for

This is a stronger fit for legal operations teams and firms with engineering capacity that want to shape connected matter workflows and access controls around infrastructure they control. It is a weaker fit for smaller firms seeking a ready-to-use intake and client portal, or for any practice that needs built-in payment collection, document storage, communications delivery or court filing. Client intake is a stated capability, but the current interface does not provide public intake.

Pros and cons

  • Pros: Broad coverage across matter operations, time, invoicing and trust records can keep related work within one system.
  • Pros: Matter assignments, ethical walls and precise portal grants support narrower access than firm-wide roles alone.
  • Pros: Append-only or compensating record changes preserve history for several sensitive financial and document events.
  • Cons: The integration boundaries stop short of performing several essential external tasks, including collecting payments, sending communications and obtaining signatures.
  • Cons: No public intake or client-facing portal UI is supplied, limiting its usefulness as a standalone client experience.
  • Cons: Real-data deployment requires substantial security, recovery, integration and legal-review work, and the maker offers no compliance guarantee.
  • Cons: General plan prices and commerce quotas are not confirmed Law Firm pricing or legal usage limits.

Alternatives

For an alternative focused on legal workflows, compare Legal Workflow Automation Software and Legal Practice Management Software lists.

  • MatterFit is worth considering when intake scoring and outcomes tracking matter more than a self-hosted, broad operations system: its free 60-day Pilot supports up to 3 users and includes Clio integration, override tracking, an outcomes dashboard and founder support.
  • Docassemble is a better match for teams seeking free, self-hosted document-automation software; hosting typically costs $10–$40 per month or more depending on performance, availability and support needs.
  • BriefBox is another option to assess for firms preferring an Android, iOS and web product with a free signup tier.
  • DecisionVault may suit teams prioritizing matter-start limits and a paid hosted product: annual-billed Solo is $83 a month for up to 10 matters started per month, while Lite is $165 a month for up to 30.
  • Checkbox is an alternative for teams evaluating paid legal workflow software with API and web access; pricing and scope are set in an order and fees may vary by authorized user type.
  • Lawmatics may be relevant to firms seeking intake and lead-management tools, with its Essential plan including 500 contacts, calendaring, custom forms, e-signature and SMS.
  • MatterSuite Matter Intake is another intake-oriented choice, with a law firm plan covering client and matter intake, team-triggered conflict checks, matter lifecycle management, timekeeping and expense capture, and billing.
  • Lexis+ is an alternative to consider for teams looking for a broader legal information and tools subscription rather than a self-hosted operations application.

Verdict

Openfront Law Firm is best for technically capable firms that want an open-source operational framework and granular control over matter access and record history. Its main reason to choose it is the combination of broad workflow coverage and self-hosting flexibility. Look elsewhere if you need a complete client-facing experience, integrated external services or a deployment that arrives with compliance and production operations already handled.

The verdict

Openfront Law Firm describes a broad operations model with detailed access controls and record history, but its integration boundaries and current interface limits are significant. The maker also cautions that the software does not guarantee legal, privacy, security or jurisdiction-specific compliance.

Questions people ask

Is Openfront Law Firm free?

The general Free plan is free, self-deploy, with full source code access and community support. The general pricing page lists paid plans from $49 a month but does not state a product-specific price.

What platforms are listed?

Openfront Law Firm is listed for web, API, and self-hosted use.

Does it provide a client portal?

The current source does not supply a client-facing portal interface or public intake UI.

What does its integration layer do?

It records provider connections, encrypted credentials, external links, communications, webhooks, API keys, and OAuth authorization. These boundaries do not themselves send messages, store documents, collect payments, file in court, calculate deadlines, or obtain signatures.

Who makes Openfront Law Firm?

The maker’s About page identifies Junaid Kabani as founder and CEO and says he started building Openship in 2019.

What the maker publishes

Access controls
The documentation describes firm memberships and roles, matter team assignments, ethical walls, and exact matter and resource grants for portal access. source
Audience
The maker describes the intended audience as law firms and legal operations teams needing connected matter work, financial records, client collaboration, document history, and integration controls in infrastructure they choose. source
Authentication extensibility
The documented integration layer implements API-key authentication, OAuth authorization-code flow with S256 PKCE, refresh-token rotation and grant-scoped agent credentials. source
Billing
Billing models rate cards and rules, time, expenses, retainers, invoices, payments, allocations and refunds. source
Client intake
Yes source
Client portal controls
Portal operations invite contacts, grant exact matter capabilities, share specific resources and revoke access without broad list reads. source
Communications
Communication records cover threads, participants, messages, delivery records and delivery attempts. source
Company headquarters
LinkedIn lists the company headquarters as Remote, US. source
Company size
LinkedIn lists Openship as a privately held internet-publishing company with 2–10 employees. source
Compliance caveat
The maker says the software does not guarantee legal-ethics, privilege, trust-accounting, privacy, retention, signature, security, or jurisdiction-specific compliance. source
Compliance limitation
The documentation says the software does not guarantee ethics, privilege, trust-accounting, privacy, retention, signature, security or jurisdiction-specific compliance. source
Current interface limits
The current source does not supply public intake or a client-facing portal UI. source
Deployment
The product documentation says to run it with Node.js, Next.js, Keystone, Prisma, and PostgreSQL, and requires explicit public and internal HTTPS origins for production. source
Deployment limits
A deployment for real firm data needs its own reviewed migration and restore procedure, managed secrets and encryption keys, tested provider adapters, monitoring, incident response, and jurisdiction-specific legal review. source
Deployment model
The product is designed to run on infrastructure chosen by the firm, with the application and PostgreSQL database deployed under organizational control. source
Documents and signatures
Document functionality includes documents, immutable versions, signature requests, signers and signature events. source
Extension path
Developers extend the product through Keystone models, reviewed migrations, narrow mutations, provider adapters, dashboard routes and explicit API, OAuth or agent scopes. source
Founded
2019 source
Founded
2019 source
Founder
The maker’s about page identifies Junaid Kabani as founder and CEO and says he began building Openship in 2019. source
Free plan
Yes source
GraphQL API
The application exposes a bounded GraphQL API with scoped queries and named operations for onboarding, intake, access, billing, trust, portal, integrations, retention and agent actions. source
HTTP security boundary
The GraphQL boundary requires JSON for ordinary POST calls, restricts multipart uploads to the configured public origin, limits bodies and list sizes, caps query depth, disables HTTP introspection and redacts internal error extensions. source
Install workflow
The documented setup starts with npm install, local PostgreSQL configuration, schema build, type checking, tests, linting and application build. source

Checked against the maker's pages on 14 Oct 2026.