BoardPAC On-Premise

Customer-hosted board meeting and governance platform with role-based meeting access.

2 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Vendor-assisted on-premises/self-hosted implementation

  2. Operated by

    Your team

    Customer and BoardPAC agree infrastructure ownership, backups, updates and support for the selected on-premises installation.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVendor-assisted on-premises/self-hosted implementation
InfrastructureServers / containers
Persistent customer-hosted board platform with browser and mobile clients; detailed backend requirements must be scoped with BoardPAC.
Licensing modelCommercial Only
BoardPAC uses commercial end-user subscription terms with usage and redistribution restrictions. Confirm the specific on-premises order and support agreement rather than applying SaaS availability terms to customer operations.
LicenseCommercial subscription software; obtain on-premises order terms

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 1 documented · 3 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The feature page advertises SSO and on-premises deployment, but does not identify the protocol or licensed on-premises configuration. Confirm both before treating a particular identity provider as supported.

On-premises SSO protocol/entitlement unresolved · Source ↗ · Reviewed 2026-11-14

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
Not confirmedEvidence and scope for Deployment artifact / IaC

BoardPAC advertises on-premises/self-hosted deployment, but the reviewed public features and terms do not supply a backend installer or automation artifact. Mobile-app connection instructions do not establish server installation; obtain the contracted backend package and vendor implementation procedure.

BoardPAC customer-managed backend artifact remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The public self-hosting statement does not specify backend CPU/RAM/storage or HA requirements. Agree the server/database topology, concurrent board users, document processing, offline-device synchronisation and backup/recovery capacity with the vendor.

BoardPAC on-premises backend sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

BoardPAC terms grant time-limited internal use of a subscription subject to the order and restrict redistribution and sublicensing. Confirm the on-premises order, user/device limits, backend entitlement, updates and support separately; general service terms do not establish the final self-hosted price.

BoardPAC public subscription framework; specific on-premises order terms require review · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The official features page explicitly offers on-premises or self-hosted deployment. Confirm the customer-operated topology and the feature set in the on-premises order, especially optional AI and video-conferencing integrations.

Category fit

Board & committee governance
Board-meeting collaboration and document access controls through a vendor-supported on-premises board platform.

Compare within Board & committee governance

  • BeleniosSelf-hosted verifiable online voting with separated election administration, credential and trustee roles.
    • Azure
    Customer-operated · Open Source / Open Core
  • FormKiQ Board and Committee Governance Directory PublisherManage board meeting documentation, agendas, resolutions, minutes, and committee records with controlled access, version management, and long-term retention.
    • AWS
    Customer-operated · Commercial Only
  • Helios VotingOpen-source verifiable election software for organizational and committee voting.
    • Heroku
    • Fly.io
    Customer-operated · Open Source / Open Core
  • Indico (CERN)CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.
    • Railway
    Customer-operated · Open Source / Open Core
  • Minute (i.AI)Open-source meeting transcription and minute generation developed for public-sector use.
    • AWS
    Customer-operated · Open Source / Open Core
  • OpenSlidesSelf-hosted assembly governance for agendas, motions, elections and meeting participation.
    • Railway
    Customer-operated · Open Source / Open Core

These products address related workflows; read their category-fit notes before comparing scope. See all of Board & committee governance →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • BoardPAC deployment within an existing Azure environment ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor explicitly states that organizations can deploy BoardPAC within their existing Azure environment. This is a vendor deployment statement rather than a public installation guide; agree the customer subscription, backend requirements, operational ownership and commercial terms before deployment.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory