AccessPoint vs. ArkCase

The short answer

ArkCase FOIA is a serious option for a US federal agency — or a state office with a federal-style process — that wants a configurable case-management platform with a public portal and reading room, intake-to-release queues, native redaction with exemption codes, and the DOJ/OIP annual and quarterly FOIA reports generated in-product, on an offering with a FedRAMP Moderate authorization and an LGPL open-source core you can inspect and self-host. Its trade-offs are the flip side of that flexibility: the free edition ships without the redaction viewer, Enterprise is priced per named user with cloud compliance requirements as an extra, and the Java, Alfresco, Solr and Pentaho stack is either a vendor cloud or a substantial platform to run yourself. AccessPoint is narrower in deployment choice and broader in scope: it runs only inside your own Microsoft 365 and Azure tenant, collects records where they already live, redacts video and audio natively, and carries privacy assessments, breach response, complaints and risk on the same audit ledger — at flat published prices.

What is ArkCase FOIA (ArkCase open-source and enterprise case management)?

ArkCase comes from Armedia LLC of Vienna, Virginia, a federal systems integrator founded in 2002 that holds service-disabled-veteran-owned and woman-owned small business designations, a GSA schedule, an 8(a) STARS III seat and ISO 27001:2022 certification. By the company's own account the platform was born from more than eight years supporting the FBI's legacy case management system, which convinced the team that a general investigative case-management product was needed; the brand is now held by ArkCase, LLC, with Armedia as implementer. The Community Edition is published on GitHub under the LGPL-3.0 licence on a Java, Spring and Tomcat stack with Solr search, ActiveMQ messaging, MySQL, Alfresco content management and Pentaho reporting. ArkCase announced a FedRAMP Moderate Authorization to Operate in October 2024, sponsored by the Postal Regulatory Commission for its eDockets system; the vendor's security materials describe TLS 1.3 and AES-256 encryption, SOC 2 Type II, NIST 800-53 alignment, Veracode Verified Standard status (October 2019), and deployment into AWS GovCloud and classified enclaves as well as customer data centres.

The FOIA solution sits on that platform. A public portal offers self-service submission, status checks and cancellation, alongside a reading room for records already released; intake can also arrive by phone, email, fax and walk-in, with scanned content OCR'd on the way in. Requests and appeals move through dynamic workflows — the product demonstration walks a request through intake, fulfill, approve, an optional general-counsel step, billing and release queues — with per-user and per-request activity monitoring and template-driven correspondence. On the review side there is a PST extractor, bulk redaction, automated content redaction that applies exemption codes through regular-expression rules, document review and e-discovery (Montana's Department of Administration paired it with Relativity in 2024), and a listed automated video and audio redaction capability. Redactions are saved as annotation overlays on the original and burned into a new version at release. Reporting is a genuine strength for federal buyers: the built-in module produces the required DOJ reports with NIEM-XML output, and release 25.09.04 added quarterly DOJ/OIP reporting of the ten oldest pending requests, appeals and consultations. Public-records customers named in the vendor's announcements and success stories include the Washington State Legislature, the DC Office of the Chief Financial Officer, Tennessee's Office of General Counsel (May 2024) and Montana's Department of Administration (July 2024); no customer count is published.

Pricing is unusually transparent for the category. The Open Source edition is free with online-only support and a viewer-only document experience; Enterprise Gold is listed at US$60 per named user per month in the cloud, with cloud compliance requirements such as SOC or CJIS as an additional cost and special pricing offered to government, education and not-for-profit buyers; Enterprise Platinum, with 24x7 support, is by quote. Annotation and redaction, online co-editing, the full Pentaho analytics suite, AI integrations such as transcription, and high-availability clustering are Enterprise-only. That is the comparison point. ArkCase is a general case-management platform configured for FOIA, and its strength is that flexibility — federal reporting, appeals, dockets and legal matters on one engine, with the code in the open. The cost is that you are paying for, or running, a platform, and responsive records are uploaded into it. AccessPoint's position is the reverse: a purpose-built access and privacy product that installs into the Microsoft 365 tenant you already run, collects records where they already are, and carries the privacy side of the same office on the same ledger.

ArkCase fact sheet

Product: ArkCase FOIA — FOIA and public-records solution on the ArkCase case-management platform; Community (open source) and Enterprise (Gold and Platinum) editions
Vendor lineage: Armedia LLC (Vienna, Virginia, founded 2002) grew ArkCase out of FBI case-management work; the brand is now ArkCase, LLC, with Armedia as implementer
Deployment: Vendor cloud with a FedRAMP Moderate ATO (October 2024, sponsored by the Postal Regulatory Commission), AWS GovCloud and other enclaves, or self-hosted on your own physical or virtual servers
Open source: Community Edition on GitHub under LGPL-3.0 — Java, Spring, Tomcat, Solr, ActiveMQ, MySQL, Alfresco, Pentaho; the annotation and redaction viewer is Enterprise-only
Pricing (published): Open Source free; Enterprise Gold US$60 per named user per month (cloud), compliance hosting requirements such as SOC or CJIS at additional cost; Enterprise Platinum by quote; government discounts offered
Market: US federal agencies and state governments with federal-style FOIA processes; named public-records customers include the Washington State Legislature, DC OCFO, Tennessee's Office of General Counsel and Montana's Department of Administration

Sources

ArkCase and AccessPoint, side by side

	ArkCase	AccessPoint
Scope	FOIA and public-records requests and appeals on a general case-management platform that also sells legal, complaint, correspondence and docket solutions	Records requests plus PIAs, AIAs, breach response with a notification calculator, complaints and appeals, and an ISO 31000-aligned privacy risk register — one product, one audit ledger
Where your data lives	ArkCase's cloud (FedRAMP Moderate), an AWS GovCloud or other enclave, or your own data centre if you run the stack yourself	Your own Microsoft 365 and Azure tenant — there is no vendor-hosted option
Records collection	Capture from web, phone, email, fax and walk-in intake; a PST extractor for mailbox exports; native connectors to more than 40 ECM repositories including Alfresco, Documentum and SharePoint	Pulled straight from SharePoint, OneDrive, Outlook, calendars, Teams chats and meeting recordings, OneNote and Copilot interaction history — plus a New-from-email flow that turns an intake-mailbox message into a request in one step
Jurisdiction rules	US federal FOIA orientation — DOJ/OIP annual and quarterly reports with NIEM-XML output generated in-product; state processes configured per implementation	136 jurisdiction packs — 57 US public-records packs covering federal FOIA, every state, DC and the populated territories, plus Canadian, UK, EU and other statutes — with deadlines, exemptions, fee schedules and letters preloaded; the statistics module lists US FOIA and Washington JLARC among the annual-reporting regimes it covers
Redaction	Native annotation-overlay redaction burned into a new version at release, exemption codes, bulk redaction and regex-driven automatic redaction — Enterprise edition only; the Community edition is viewer-only	Browser-native studio with statutory exemption tagging and fall-backs, request-scoped find-and-redact patterns, tenant detection rules, and optional AI-proposed redactions that always land in human review — every feature in every tier
Video & audio redaction	Listed as automated video and audio redaction on the FOIA solution page; the engine, licensing, and how an exemption code attaches to a time span are not described in its published documentation	Native: box, blur and pixelate for the picture; mute, bleep and voice distortion for the sound; in-tenant face detection and tracking; transcript-anchored proposals; the exemption recorded on every span, with a time-based redaction log and an ML-use disclosure in the release — no separate licence
Audit trail	Per-user and per-request activity monitoring and application audit logging	Hash-chained, append-only audit ledger with server-side integrity verification, plus court-ready case audit exports (audit log CSV, manifest, AI-involvement disclosure)
Pricing	Open Source free; Enterprise Gold US$60 per named user per month in the cloud, compliance hosting extra; Platinum by quote	Flat annual pricing by organization size, published on the site, no per-user metering; installed from Microsoft AppSource

Competitor capabilities vary by product edition and configuration; this table reflects each product's public positioning as of 2026-09-04.

Where ArkCase fits

A fair comparison cuts both ways — ArkCase is a reasonable choice when:

You are a US federal agency that files DOJ/OIP annual and quarterly FOIA reports. ArkCase generates them in-product, including NIEM-XML output and the quarterly ten-oldest pending requests, appeals and consultations report added in release 25.09.04. AccessPoint's statistics module covers US FOIA annual reporting among many regimes, but check its output against your OIP submission format before deciding — ArkCase was built around that filing.
You need a FedRAMP-authorized offering, a classified enclave, or code you can read and host yourself. ArkCase has a FedRAMP Moderate ATO, is described as deployable into AWS GovCloud, NIPR, SIPR and JWICS, and publishes its Community Edition under LGPL-3.0 on GitHub. AccessPoint runs only inside your Microsoft 365 and Azure tenant; if your authority to operate depends on FedRAMP paperwork or an air-gapped network rather than Microsoft's platform attestations, ArkCase fits and AccessPoint does not.
You already run Alfresco, Documentum or another enterprise content repository, or review productions in Relativity. ArkCase natively connects to more than 40 ECM repositories and has shipped a Relativity pairing for public-information work, so a records program anchored in those systems keeps its centre of gravity.
The public portal and reading room are your top requirement. ArkCase's self-service portal — submit, check status, cancel — and its reading room for released records are shipped today, while AccessPoint's requestor self-service portal is on the public roadmap. If letting requesters file and track their own requests is non-negotiable this budget cycle, that is a straightforward reason to choose ArkCase.

Where AccessPoint differs as a ArkCase alternative

No platform to run, no cloud to onboard ArkCase is a Java, Alfresco, Solr and Pentaho platform you either pay to have hosted or stand up yourself. AccessPoint installs into the Microsoft 365 tenant you already operate — App Service, Azure SQL and Blob Storage in your own subscription — and authenticates through your existing Microsoft Entra ID, so the database, documents and audit history never leave your tenancy and your existing security stack governs everything.

Collection without PST exports or repository connectors Search SharePoint, OneDrive and Outlook from the request and attach records directly — including calendars, Teams chats and meeting recordings, OneNote and Copilot interaction history — instead of extracting PSTs or wiring up a content-repository connector. A New-from-email flow turns a message in your intake mailbox into a fully formed request in one step.

The whole mandate, not just the request queue Privacy impact and algorithmic impact assessments, breach response with a notification calculator, complaints and appeals, and an ISO 31000-aligned privacy risk register run on the same platform and the same hash-chained audit ledger as your public-records requests — with 136 jurisdiction packs preloading the deadlines, exemptions and letters for each statute.

Flat pricing, every feature in every tier ArkCase's free edition is viewer-only, and Enterprise is metered per named user with compliance hosting as an extra. AccessPoint is priced flat and annually by organization size, published on the site, with document, video and audio redaction included rather than gated to a higher edition — and it installs from Microsoft AppSource.

Migrating from ArkCase to AccessPoint

Leaving ArkCase — or consolidating a federal-style FOIA queue and a privacy program into one system? AccessPoint imports historical caseloads from any export that reaches Excel, and ArkCase's search-results export and Pentaho reporting (or, if you self-host the open-source edition, the MySQL database itself) already put the request data within reach.

Export your request history from ArkCase — the search-results export or a Pentaho report — to Excel; request identifiers, requester details, queue status and dates are enough to start.
Download AccessPoint's import template from Settings → Data import & export; it is generated with your own tenant's type codes, and your existing request numbers persist as legacy references (or stay official if your published log requires it).
Upload and validate — a per-row created / skipped / errors report runs before anything imports, with a fix-and-reupload error workbook; imports are create-only, so corrected files can be re-run safely.
Stage documents in the migration-staging container in your own Azure storage, folder-per-case with AzCopy — exported from Alfresco or whichever repository ArkCase was connected to — listed on the Documents tab with optional MD5 hash verification for chain of custody.
Import in the background; records arrive historical, with no notifications, no recomputed deadlines, and an Imported audit-trail entry on every record, so in-progress cases continue without a cutover.

Rehearse against a test tenant first — the Export tab produces the same workbook the importer accepts, so a trial migration validates end to end before you touch production.

Plan your migration → · Data Import & Export guide · Migration & onboarding services

Questions people ask about ArkCase and AccessPoint

Is ArkCase really open source, and what is in the free edition?

Yes — the ArkCase Community Edition is on GitHub under the LGPL-3.0 licence, on a Java, Spring and Tomcat stack with Solr, ActiveMQ, MySQL, Alfresco and Pentaho. The vendor's own comparison lists the free edition as viewer-only with online support only; annotation and redaction, online co-editing, the full Pentaho analytics suite, AI integrations such as transcription, and high-availability clustering are Enterprise features. Enterprise Gold is published at US$60 per named user per month in the cloud, with compliance hosting requirements such as SOC or CJIS as an additional cost and special pricing for government; Platinum is by quote.

How is AccessPoint different from ArkCase FOIA?

Shape and scope. ArkCase is a general case-management platform configured for FOIA — flexible, open at the core, FedRAMP Moderate-authorized, and strong on US federal reporting — that you either have hosted or run yourself, and into which responsive records are uploaded or connected through repository integrations. AccessPoint is a purpose-built access and privacy product that installs from Microsoft AppSource into the Microsoft 365 tenant you already run: records are collected straight from SharePoint, OneDrive, Outlook and Teams; the database, documents and hash-chained audit ledger stay in your own Azure subscription; document, video and audio redaction are native and included; and privacy impact and algorithmic impact assessments, breach response, complaints and a risk register run alongside requests. Pricing is flat and annual by organization size rather than per named user.

Does AccessPoint produce US FOIA reports and have a public portal like ArkCase?

Partly, and honestly. AccessPoint's statistics module turns request, privacy and complaint data into the figures an office needs for management oversight and annual reporting, and lists US FOIA and Washington JLARC among the regimes it covers — but ArkCase's DOJ/OIP reporting, with NIEM-XML output and the quarterly ten-oldest report, is built specifically around the federal filing, so a federal agency should check AccessPoint's output against its OIP submission before deciding. On the portal, ArkCase's self-service portal and reading room are shipped today; AccessPoint's requestor self-service portal is on the public roadmap, and intake currently runs through your team, including a New-from-email flow that turns an intake-mailbox message into a fully formed request.

Is AccessPoint an ArkCase alternative for a state or local agency?

For an agency that runs Microsoft 365, usually yes — and the fit improves the further you are from the federal filing calendar. AccessPoint ships a jurisdiction pack for federal FOIA, every state, DC and the populated territories, preloading each statute's deadlines, exemptions, fee schedules and letter templates, and it adds the privacy work the same office increasingly owns. Where ArkCase remains the better answer: you need FedRAMP-authorized hosting or a classified enclave, you want to self-host open-source code, your records live in Alfresco or Documentum, or a shipped public portal and reading room is the deciding requirement.

Can we import our ArkCase history into AccessPoint?

Yes. Export your request history from ArkCase — the search-results export, a Pentaho report, or the database itself if you self-host — to Excel, map it into AccessPoint's tenant-generated import template, and read the per-row validation report before anything commits. Old request numbers persist as legacy references, requester contacts import alongside their requests, and documents exported from the connected repository stage through the migration-staging container in your own Azure storage with optional MD5 hash verification. Imported records arrive historical: no notifications fire, nothing recomputes, and every record carries an Imported audit-trail entry.

Competitor information on this page is drawn from public sources — vendor websites, government reports, and press coverage — and was last reviewed in 2026-09-04. Products evolve, and a comparison is never the whole story: capabilities vary by edition and configuration. Spot something out of date? Tell us and we'll correct it.