HighWire Press

Name: HighWire Press
Brand: HighWire Press

We turn 30 this year✨ Celebrate with us 30 years of building a community of scholarly publishers.

Est 1995|Valuation $22.4M

LinkedIn 9K|Website|Web traffic 4K|FTEs 70

Published Jun 25, 2026

01Common complaints

1) When transparent, self-serve pricing and an immediate purchase path are required - HighWire’s core modules do not have public price lists; procurement workflows that require published rate cards may prefer alternatives with transparent pricing. 2) When the publisher is a small operation with limited internal operations staff - If the organization cannot support an implementation project and governance process, a lower-cost, opinionated workflow tool or community solutions may be a better fit. 3) When public security/compliance documentation is mandated prior to engagement - If the procurement process requires public SOC 2 Type II summaries, ISO scope statements, or pen test attestations before any evaluation, this may be a barrier; expect NDA-based diligence for those artifacts. 4) When only a single narrow function is required - If the requirement is limited to peer review alone, a specialist submission system may deliver lower cost and faster deployment.

Poor fit signals

Very small publishers managing a single title and focused primarily on minimizing ongoing cost and implementation effort.
Teams that require fully self-serve SaaS with minimal professional services.
Organizations that require publicly documented security attestations prior to any vendor engagement and where those attestations are non-negotiable without extensive NDA-level diligence.

Publicly acknowledged limitations

Vendor public pages are primarily marketing-focused and do not present an exhaustive list of limitations.

Practical limitations / risks to test during evaluation

- Implementation complexity: obtain detailed timelines, migration tooling, and internal resource estimations. - Integration depth: confirm API maturity, rate limits, authentication and provisioning patterns, and support for required third-party integrations (ORCID, Crossref, iThenticate, analytics, payments). - Analytics and reporting: validate COUNTER compliance, portfolio-level analytics, BI exports, and integration with existing analytics pipelines. - Vendor lock-in and data portability: ensure contractual clarity on content exports, reviewer data, audit logs, and identity data formats and extraction processes.

02Why they buy

Capabilities supported by available evidence

Coverage of multiple publishing lifecycle areas: hosting, submission, identity, subscriptions/fulfillment, and analytics as described in product materials.
Configurability and workflow tailoring: stated support for publisher-specific editorial and production flows.
Documented publisher engagements and case studies illustrating migrations and platform usage with established publishers and societies.

Claims requiring validation

Operational metrics such as uptime and performance (vendor-reported figures) should be validated through SLAs, third-party monitoring, and reference checks.

Areas where competitors may have stronger propositions

Transparent public pricing and simpler onboarding for smaller publishers.
Larger installed base familiarity that can reduce training overhead for editorial staff.

03Field reports

What’s available (and what’s not)

HighWire Press does not have a prominent presence on major SaaS review platforms (G2, TrustRadius, Gartner Peer Insights) based on the research performed for this report. - Gartner Peer Insights: no clear HighWire Press product page was accessible in results during the research queries. - G2: no clear HighWire Press listing was found during searches. - TrustRadius: no clear HighWire Press listing was found during searches. Available review-like evidence therefore consists primarily of: 1) Vendor-published testimonials and case studies (marketing-selected content). 2) Employee reviews on job sites (mixed signals). 3) Industry commentary / independent writeups (limited coverage).

Vendor testimonials (marketing-selected)

Examples from HighWire’s website include customer quotes emphasizing operational continuity and collaborative relationships. These are curated on vendor pages and should be treated as vendor-selected evidence.

Case-study style outcomes (vendor-published)

Reported outcomes include uptime and traffic handling during peak events, migration time reductions, and changes in organic referrals. These outcomes are published by the vendor; methodologies and attribution are not independently documented in the public case studies and should be validated in reference checks.

Employee reviews (mixed; relevant as a signal)

Employee reviews visible on job boards show a range of perspectives: - Positive: reviewers describing a professional work environment and engagement in product and technical work. - Negative: older reviews from several years ago describe layoffs and operational challenges, which indicate an area for due diligence on historical incident and staffing trends. These employee perspectives are not customer satisfaction reviews, but they can be informative regarding support capacity, staff turnover, and operational execution.

Community/social discussions

Searches for "HighWire" and "Highwire" on community forums returned noise due to naming ambiguity; many results refer to unrelated organizations (e.g., PR agencies, compliance platforms). This ambiguity reduces the reliability of community sentiment searches for HighWire Press specifically. Takeaway: procurement teams should prioritize direct vendor reference checks with comparable publishers rather than rely on general community forums for sentiment about HighWire Press.

1) Cold Spring Harbor Laboratory — bioRxiv/medRxiv hosting

Vendor report: HighWire hosted large-scale preprint servers and scaled during pandemic traffic spikes, reporting strong availability and heavy page view volumes.
Critical view: these metrics are vendor-reported. Recommended validation steps include independent uptime monitoring, a technical architecture explanation (CDN strategy, caching, search performance), and review of traffic/availability SLAs.

2) Anonymized scientific society — workflow modernization

Vendor report: reported reductions in turnaround time during transition (e.g., a reported substantial reduction with an ambitious target for a specific stage).
Critical view: anonymized case studies limit external validation. Request baseline definitions, measurement windows, and follow-up data to determine whether operational gains were sustained and which process changes were responsible.

3) BMJ partnership renewal

Vendor report: a long-standing partnership and subsequent renewal indicate continued engagement over time.
Critical view: renewal indicates an ongoing vendor relationship but does not disclose total cost, internal resource allocations, or comparative alternatives considered prior to renewal.

04Best fit

Best-fit organizations

Mid-to-large scholarly publishers, societies, or university presses managing multiple journals (from several to many), complex subscription/entitlement models, multi-format sites (journals, reference works, multimedia), and higher-traffic properties where SEO and discovery are priorities.

Company size (practical ranges)

Fits organizations that can support a platform partner relationship: broadly, publishers with significant digital operations and revenue. Smaller societies with outsourced production may also fit depending on budget and governance.

Roles and personas

Decision makers: VP/Director of Publishing Operations, Head of Platforms/Technology, Managing Director, CFO (for TCO decisions).
Influencers: editorial leadership, production managers, librarians/consortia access stakeholders, analytics/marketing operations.

Strong fit criteria

Need for configurable editorial and production workflows.
Requirement for institutional identity and entitlement management at scale.
Need for integrated hosting combined with editorial workflows and analytics.

05The pitch

What the product does (core value proposition)

HighWire Press (often branded as HighWire) provides a suite of B2B software and services for scholarly and STM (scientific, technical, medical) publishing across the publishing lifecycle: - Manuscript submission & peer review: BenchPress - Content hosting / publishing platform: Scolaris (and legacy/adjacent hosting products such as JCore) - Identity & access management: Sigma - Subscriptions / fulfillment / ecommerce & BI: THINK365 - Editorial & production workflow: products listed under Editorial & Production (e.g., DigiCorePro, DigiEdit) - Analytics: Impact Vizor, Insight Vizor, ScholarlyStats (as listed on HighWire’s services catalog) HighWire is presented as a configurable and interoperable platform and services provider for publishers that require reliability, scalability, and workflow customization rather than a single standardized SaaS offering.

Target market and positioning

Primary buyers: scholarly publishers, university presses, professional societies, associations, STM publishers, and platforms such as preprint servers.
Use-case focus: high-volume journal programs, multi-format content sites, and publishers needing improved discovery/user experience, identity/authentication, and integrations.
Positioning: a platform-and-services model with domain experience in scholarly publishing.

Get a comprehensive analysis of HighWire Press including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Jun 25, 2026

01Common complaints

When transparent, self-serve pricing and an immediate purchase path are required

HighWire’s core modules do not have public price lists; procurement workflows that require published rate cards may prefer alternatives with transparent pricing.

When the publisher is a small operation with limited internal operations staff

If the organization cannot support an implementation project and governance process, a lower-cost, opinionated workflow tool or community solutions may be a better fit.

When public security/compliance documentation is mandated prior to engagement

If the procurement process requires public SOC 2 Type II summaries, ISO scope statements, or pen test attestations before any evaluation, this may be a barrier; expect NDA-based diligence for those artifacts.

When only a single narrow function is required

If the requirement is limited to peer review alone, a specialist submission system may deliver lower cost and faster deployment.

Poor fit signals

Very small publishers managing a single title and focused primarily on minimizing ongoing cost and implementation effort.
Teams that require fully self-serve SaaS with minimal professional services.
Organizations that require publicly documented security attestations prior to any vendor engagement and where those attestations are non-negotiable without extensive NDA-level diligence.

Publicly acknowledged limitations

Vendor public pages are primarily marketing-focused and do not present an exhaustive list of limitations.

Practical limitations / risks to test during evaluation

Implementation complexity: obtain detailed timelines, migration tooling, and internal resource estimations.
Integration depth: confirm API maturity, rate limits, authentication and provisioning patterns, and support for required third-party integrations (ORCID, Crossref, iThenticate, analytics, payments).
Analytics and reporting: validate COUNTER compliance, portfolio-level analytics, BI exports, and integration with existing analytics pipelines.
Vendor lock-in and data portability: ensure contractual clarity on content exports, reviewer data, audit logs, and identity data formats and extraction processes.

02Why they buy

Capabilities supported by available evidence

Coverage of multiple publishing lifecycle areas: hosting, submission, identity, subscriptions/fulfillment, and analytics as described in product materials.
Configurability and workflow tailoring: stated support for publisher-specific editorial and production flows.
Documented publisher engagements and case studies illustrating migrations and platform usage with established publishers and societies.

Claims requiring validation

Operational metrics such as uptime and performance (vendor-reported figures) should be validated through SLAs, third-party monitoring, and reference checks.

Areas where competitors may have stronger propositions

Transparent public pricing and simpler onboarding for smaller publishers.
Larger installed base familiarity that can reduce training overhead for editorial staff.

03Field reports

What’s available (and what’s not)

HighWire Press does not have a prominent presence on major SaaS review platforms (G2, TrustRadius, Gartner Peer Insights) based on the research performed for this report.

Gartner Peer Insights: no clear HighWire Press product page was accessible in results during the research queries.
G2: no clear HighWire Press listing was found during searches.
TrustRadius: no clear HighWire Press listing was found during searches.

Available review-like evidence therefore consists primarily of:

Vendor-published testimonials and case studies (marketing-selected content).
Employee reviews on job sites (mixed signals).
Industry commentary / independent writeups (limited coverage).

Vendor testimonials (marketing-selected)

Case-study style outcomes (vendor-published)

Reported outcomes include uptime and traffic handling during peak events, migration time reductions, and changes in organic referrals. These outcomes are published by the vendor; methodologies and attribution are not independently documented in the public case studies and should be validated in reference checks.

Employee reviews (mixed; relevant as a signal)

Employee reviews visible on job boards show a range of perspectives:

Positive: reviewers describing a professional work environment and engagement in product and technical work.
Negative: older reviews from several years ago describe layoffs and operational challenges, which indicate an area for due diligence on historical incident and staffing trends.

These employee perspectives are not customer satisfaction reviews, but they can be informative regarding support capacity, staff turnover, and operational execution.

Community/social discussions

Takeaway: procurement teams should prioritize direct vendor reference checks with comparable publishers rather than rely on general community forums for sentiment about HighWire Press.

1) Cold Spring Harbor Laboratory — bioRxiv/medRxiv hosting

Vendor report: HighWire hosted large-scale preprint servers and scaled during pandemic traffic spikes, reporting strong availability and heavy page view volumes.
Critical view: these metrics are vendor-reported. Recommended validation steps include independent uptime monitoring, a technical architecture explanation (CDN strategy, caching, search performance), and review of traffic/availability SLAs.

2) Anonymized scientific society — workflow modernization

Vendor report: reported reductions in turnaround time during transition (e.g., a reported substantial reduction with an ambitious target for a specific stage).
Critical view: anonymized case studies limit external validation. Request baseline definitions, measurement windows, and follow-up data to determine whether operational gains were sustained and which process changes were responsible.

3) BMJ partnership renewal

Vendor report: a long-standing partnership and subsequent renewal indicate continued engagement over time.
Critical view: renewal indicates an ongoing vendor relationship but does not disclose total cost, internal resource allocations, or comparative alternatives considered prior to renewal.

04Best fit

Best-fit organizations

Mid-to-large scholarly publishers, societies, or university presses managing multiple journals (from several to many), complex subscription/entitlement models, multi-format sites (journals, reference works, multimedia), and higher-traffic properties where SEO and discovery are priorities.

Company size (practical ranges)

Fits organizations that can support a platform partner relationship: broadly, publishers with significant digital operations and revenue. Smaller societies with outsourced production may also fit depending on budget and governance.

Roles and personas

Decision makers: VP/Director of Publishing Operations, Head of Platforms/Technology, Managing Director, CFO (for TCO decisions).
Influencers: editorial leadership, production managers, librarians/consortia access stakeholders, analytics/marketing operations.

Strong fit criteria

Need for configurable editorial and production workflows.
Requirement for institutional identity and entitlement management at scale.
Need for integrated hosting combined with editorial workflows and analytics.

05The pitch

What the product does (core value proposition)

HighWire Press (often branded as HighWire) provides a suite of B2B software and services for scholarly and STM (scientific, technical, medical) publishing across the publishing lifecycle:

Manuscript submission & peer review: BenchPress
Content hosting / publishing platform: Scolaris (and legacy/adjacent hosting products such as JCore)
Identity & access management: Sigma
Subscriptions / fulfillment / ecommerce & BI: THINK365
Editorial & production workflow: products listed under Editorial & Production (e.g., DigiCorePro, DigiEdit)
Analytics: Impact Vizor, Insight Vizor, ScholarlyStats (as listed on HighWire’s services catalog)

HighWire is presented as a configurable and interoperable platform and services provider for publishers that require reliability, scalability, and workflow customization rather than a single standardized SaaS offering.

Target market and positioning

Primary buyers: scholarly publishers, university presses, professional societies, associations, STM publishers, and platforms such as preprint servers.
Use-case focus: high-volume journal programs, multi-format content sites, and publishers needing improved discovery/user experience, identity/authentication, and integrations.
Positioning: a platform-and-services model with domain experience in scholarly publishing.

Get a comprehensive analysis of HighWire Press including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →