Deployment and delivery

Choose where it runs. Launch it properly.

There are two ways to run Archively: a managed service, or a dedicated environment you can control. The product is the same in both. Every first year includes a scoped launch.

Two deployment models

Managed by Archively, or controlled by you.

Both run the same platform. The difference is who operates the infrastructure and where the records live.

Archively Cloud

The managed multi-tenant platform, for institutions that want Archively to operate the infrastructure.

Who operates it: Archively runs and maintains the platform for you.
Where data lives: The managed Archively cloud, a multi-tenant service.
Cost shape: Annual platform subscription.

Archively Private

A dedicated Archively-managed environment, or a customer-controlled self-hosted deployment on Linux.

Who operates it: Archively runs a dedicated environment, or your team runs it self-hosted on Linux.
Where data lives: A single-tenant environment Archively manages, or your own Linux infrastructure that you control.
Cost shape: Higher annual subscription, plus infrastructure and the launch engagement.

Identical in both

The product is the same in every deployment.

Standards-based exports: Dublin Core, EAD, MODS, METS with PREMIS, and BagIt. Your data leaves in open formats at every stage.
SAML SSO and MFA: The same single sign-on and multi-factor authentication in both deployments.
The review workflow: The same role pipeline: AI review, quality review, rights clearance, then publish.
Staff work and public access: The same cataloging modules for staff and the same branded portal for researchers.

Delivery

Every first year includes Archively Launch.

Moving a collection is real work, and Archively Launch is where it happens. Launch is the scoped first-year engagement that makes the platform real for your institution, delivering migration, configuration, training, portal setup, and go-live as owned work you can plan against.

Launch is a one-time engagement. Renewal years carry the subscription, not the launch again.

01: We move your records off the current system using standards-based import.
02: We set up the hierarchy, vocabularies, roles, and workflow stages to match your practice.
03: We train the staff who will catalog, review, clear rights, and publish.
04: We stand up your branded public portal on an archively.ai address.
05: We move the configured system into production and hand over a running archive.

Archively Extensions

Separately scoped. Net-new integrations, workflows, public interfaces, or vertical modules, delivered as their own engagement with a written scope. Extensions are optional and never assumed in the first-year budget.

Planning

One published range, quoted directly.

Deployments vary, so each first year is scoped to fit. Use the range to size a first-year budget, then request a written estimate for your exact scope.

Planning range

$35,000–$75,000

Typical first-year managed engagements, including the annual platform subscription and standard Archively Launch services.

Archively Private, complex migration, and Archively Extensions are scoped separately.

Map your infrastructure and data-exit requirements before the evaluation.

Request an evaluation Request a live archive first

A working setup using your records, not a sales presentation.