Compare archivarix and KeystoneJS on pricing, features, platforms, and ratings — both CMS tools, Pay-per-use credit-balance pricing: roughly $0.25 for a…
At a Glance
archivarix
KeystoneJS
Primary category
CMS
CMS
Rating
Not documented
Not documented
Pricing model
Pay-per-use credit-balance pricing: roughly $0.25 for a Wayback Machine restoration up to 200 files, then about $10 per additional 1,000 files, with live-site downloads billed on a similar tiered file-count basis. No flat monthly subscription tiers are published.
Open Source
Starting price
Not documented
Free
Free plan
Not documented
Not documented
Free trial
Not documented
Not documented
Platforms
Web
Web
Team collaboration
Not documented
Not documented
AI features
Not documented
Not documented
Public API
Yes
Yes
Pricing Compared
Starting price reflects the lowest paid tier, not the full cost for every team size or usage level.
archivarix
No individual plan breakdown documented yet.
KeystoneJS
Open Source — Free N/A
Pros & Cons
archivarix
Pros
Can rebuild a working copy of a site purely from Wayback Machine archives, useful when the original site and its files are gone
Pay-per-use pricing means occasional users aren't locked into a recurring subscription
Bundled CMS and export options (WordPress/Joomla-compatible, static HTML, JSON/CSV/XML) give flexibility in what you do with the recovered content
Built-in optimization (image compression, minification, link fixing, tracker/ad removal) saves manual cleanup after a restore
Cons
Detailed subscription/plan pricing isn't published on the marketing site — costs are pay-per-file via an account balance, which makes upfront budgeting harder
Wayback Machine restorations are only as complete as what the Internet Archive actually captured, so some pages, assets, or dynamic functionality may not recover cleanly
The bundled Archivarix CMS is a niche, proprietary system rather than a mainstream platform, which may limit long-term support/ecosystem options
KeystoneJS
Pros
Completely free, open-source, self-hosted with no licensing fees
GraphQL API and admin UI generated automatically from schema
Strong TypeScript support and Prisma-based migrations
Fine-grained, code-defined access control
Backed by an experienced consultancy (Thinkmill) with enterprise delivery history
Cons
No official managed hosting offering from the Keystone project
Requires Node.js and database operational expertise to self-host
Smaller ecosystem and plugin marketplace than Strapi or WordPress
GraphQL-first design has a learning curve for teams used to REST
Migration from older Keystone (v5/Express/MongoDB) versions requires significant rework
Use Cases
archivarix
KeystoneJS
Custom application backends — Development teams use KeystoneJS to build backends for web and mobile applications with a generated GraphQL API.
Content-driven websites — Teams build static and dynamic marketing sites and blogs powered by Keystone's content model and admin UI.
Multi-channel content distribution — Organizations use Keystone's GraphQL API to distribute content across web, mobile and other channels from one source.