Student Authorship Verification Software Pricing: A University's Total-Cost Guide

Short answer: There is no meaningful single price for student authorship verification software without specifying the number of learners, how they will submit work, which writing environments they use, who can review the evidence, and how long records must be retained. Before comparing vendor quotes, universities should calculate the total cost per participating learner and per completed, reviewable submission—not simply the advertised licence fee.

AuthMarks offers free individual accounts and quote-based institutional plans. Its public pricing page says institutional scope depends on seats, integrations and retention. It does not publish an institutional per-student tariff, and this guide does not invent one.

Disclosure: AuthMarks produces writing-provenance software and publishes this guide. This is an evaluation framework, not independent pricing research or a claim that AuthMarks is cheaper than any named competitor. Pricing and terms may change; obtain a written quote.

For a broader comparison of product approaches before requesting pricing, start with the university authorship verification software buyer's guide.

Why price-per-student is only part of the equation

Imagine two universities each licence a tool for 10,000 learners. University A uses it in an optional writing-support initiative; University B requires writing-process records for every essay across several departments. The same seat count may generate dramatically different support requests, evidence volumes and review work.

Ask for at least six price components:

1. Licence basis: students, active users, concurrent users, course sections, submissions, or institution-wide access.
2. Minimum commitment: annual minimums, faculty minimums, pilot conditions and renewal rules.
3. Integration: LTI 1.3 registration, tenant setup, staging environments, support and any implementation fees.
4. Evidence storage: retention period, replay/event-log tier, archive retrieval and export charges, if any.
5. Review and governance: instructor dashboards, permission tiers, audit access, policy controls and administrator training.
6. Exit and transition: data export, deletion, verification after contract end and migration to another platform.

A cheap licence can become expensive if instructors need extensive manual review. An expensive licence may be appropriate if it replaces a costly administrative workflow—but that conclusion must be measured locally, not assumed.

What does AuthMarks charge?

The published model distinguishes personal use from institutional workflow:

Category	Publicly described offer	Budget implication
Individual writer	Free account with writing capture, named attestation and a sealed record	No published charge for the individual core plan
Educational institution	Quote based on seats, integration and retention needs	Request institution-specific terms and deployment scope
Institution workflow	LTI 1.3 integration, class-level Action Center, policies and roles, extended review controls	Confirm included modules and support obligations in writing
Business/enterprise	Contact sales; additional hosting/key-management options described	Do not assume enterprise options are included in an education quote

This information comes from AuthMarks pricing and AuthMarks for institutions. No price or payment schedule is implied by the free student plan. An institution should separately confirm whether and how it is charged for institutional administration.

To obtain a scope-specific quote, describe your intended cohort and LMS to sales@authmarks.com. A 30-day pilot design can help you define the scope before you commit to a long-term contract.

A simple total-cost model

Use this formula for a comparable annual budget:

Annual total cost = licence + implementation + integration + training + additional storage/retention + internal support + review labour + exit costs (if applicable).

Then calculate:

Effective annual cost per participating learner = annual total cost ÷ unique participating learners.

Effective cost per reviewable submission = annual total cost ÷ submissions for which the expected evidence was successfully available.

Do not divide by every enrolled learner if half of them never use the product. And do not count a submitted document as a successful provenance record if the capture was never activated or the evidence is inaccessible to reviewers.

Illustrative example — not a vendor quote

Suppose a pilot expansion budget includes the following hypothetical annual figures, all in an arbitrary local currency:

Cost item	Hypothetical amount
Licence and platform	18,000
Setup and support	3,000
Faculty training	2,000
Internal administrative time	4,000
Additional review labour	7,000
Total	34,000

If 2,000 learners actively participate, the illustrative cost is 17 per participating learner. If the same initiative generates 8,500 genuinely reviewable submissions, the illustrative cost is 4 per reviewable submission.

These numbers are only a calculation exercise; they are not AuthMarks prices or market estimates. Replace each figure with a vendor quote or your institution's own measured workload.

Compare the economics of three different deployment models

Option A: Student-controlled, optional use

Students choose to record writing and share provenance when helpful. This minimizes institutional setup but can leave uneven participation. Measure adoption, supported devices and whether staff can interpret the evidence without bespoke training.

Option B: Faculty or department pilot

A small number of courses use the same assignment instructions, review workflow and retention policy. This often produces the clearest evidence of whether the tool helps with real academic decisions. Compare staff time against your current workflow rather than against an imaginary zero-cost process.

Option C: Institution-wide rollout

A large deployment requires accessibility review, privacy and records approval, integration governance, helpdesk readiness, instructor training, equitable alternative arrangements, and a predictable support contract. The project budget is wider than the software invoice.

Questions that materially change a quote

Send vendors a single written request covering:

• How many enrolled learners will be eligible? How many are expected to actively record work?
• How many assignment submissions, per course and per year, should be in scope?
• Is a sealed file, a replay view, or both required? What are the export formats?
• Which LMS and which writing environments must work? Which are pilot-only or early-access?
• Will staff require evidence review only on an exception basis, or for every assignment?
• What happens if a student refuses recording, lacks a compatible device, works offline or uses assistive technology?
• What data is retained, where, for how long, and how can it be exported or deleted?
• Does pricing include onboarding, support, accessibility testing, security review and contract exit?
• What is the cost if participation doubles or submission volumes exceed assumptions?
• Is there a separate charge for gradebook integration, advanced forensic review or custom hosting?

Request all vendors to quote against the same scope. A vendor selling per-seat access is not directly comparable to one selling per-submission evidence unless both have been translated into a cost per successful workflow.

What should the pilot measure before a purchasing decision?

An institution can estimate return on investment only after observing real costs and effects. Record:

Metric	Measurement method	Why it matters
Activation rate	Learners who explicitly enable capture ÷ invited learners	Describes adoption and consent behaviour
Reviewable record rate	Records with accessible, interpretable evidence ÷ submitted assignments in scope	Exposes practical capture limits
Instructor review minutes	Time study across routine and escalated cases	Often dominates operating cost
Support tickets	Tickets by category per 100 participating learners	Estimates helpdesk demand
Accessibility exceptions	Approved alternative workflows and unresolved barriers	Tests whether rollout is equitable
Export/verification success	Independent staff confirm receipt and validation of sample records	Tests evidence portability
Student understanding	Brief post-assignment survey	Tests whether consent and the purpose of recording were clear

Do not present a reduction in misconduct allegations as proof that misconduct itself fell. That inference would require a much more rigorous evaluation design.

Frequently asked questions

Is AuthMarks free for students?

The public pricing page describes a free individual core account. Institutional purchasing, integrations and governance are a separate commercial conversation. Confirm access conditions and contractual language at the point of deployment.

Does AuthMarks publish university licence prices?

Not on the public pricing page checked on 3 November 2026. Institutions should request a written quote based on actual use and required controls.

Is LTI integration an additional fee?

Public product pages describe LTI 1.3 support, but do not establish a universal integration fee or promise that every institution-specific deployment is cost-free. Ask for a quote that identifies integration, onboarding and activation costs expressly.

Is software cost the same as cost of preventing cheating?

No. Writing-process evidence may support fairer evaluation, but no product alone prevents all misconduct or makes disciplinary decisions. Policy design, student support and human review remain necessary.

Next step: request a quote with a meaningful scope

If you are preparing an RFI or a budget request, begin with the student authorship-verification procurement checklist and the university pilot playbook. They will help you request comparable proposals, rather than vague list prices.

Evaluating AuthMarks? See the institutional workflow, review current pricing or contact sales@authmarks.com with your institution, LMS, expected cohort size and evidence-retention needs.

Related: Authorship verification software buyer's guide · University pilot playbook · Procurement checklist