Choose where your institution's repository files live
Connect existing storage, use InRep Cloud, or operate the highest-tier InRep Campus application on your institution server. Every institution's rollout is different, so pricing is prepared as a tailored quote rather than a fixed rate — billing term and length are agreed as part of your proposal, not chosen here.
CO
InRep ConnectLowest tier
Best for higher institutions that already keep files in Google Drive, OneDrive, SharePoint, DSpace or an institutional server and need clean metadata, search, workflow and link tracking.
Custom quotePriced to your institution's size, storage and support needs
Google Drive, OneDrive, SharePoint, DSpace and institutional server links
External link health checks and broken link alerts
Institution, faculty, department and programme structure
Public discovery pages and national search inclusion
Public submission, metadata scoring and library review workflow
Citation export, sitemap and OAI-PMH metadata endpoint
Access request tracking for controlled external records
Standard AI: title, abstract and keyword suggestions, plus repository Q&A over public metadata
CL
InRep CloudMiddle tier
Best for higher institutions that want documents uploaded directly into InRep Scholar private storage with protected viewing, analytics, backups and the complete hosted repository workflow.
Custom quotePriced to your institution's size, storage and support needs
Premium self-hosted deployment for institutions that require local file ownership, a institution-operated repository server, central discovery federation, signed licensing and controlled release management.
Custom quotePriced to your institution's size, storage and support needs
Institution-controlled database, files, domain and backups
Signed purchase, subscription and offline license controls
Federated metadata discovery on InRep Scholar
Open, view-only, metadata, restricted, private and embargo access policies
Node health, sync diagnostics, release updates and rollback support
Advanced audit, compliance, analytics and export capabilities
Priority implementation support for ICT, registry and library teams
Need procurement documentation or a bank-transfer invoice?We can prepare a formal quote around the selected term, deployment, migration, and support requirements.
The tiers are different infrastructure and ownership arrangements before they are different price points. This is the detail behind that choice.
Deployment responsibility comparison across InRep Connect, InRep Cloud, and InRep Campus
Responsibility
InRep Connect
InRep Cloud
InRep Campus
File storage location
Stays in your existing systems — Google Drive, OneDrive, SharePoint, DSpace, or an institutional server. Inrep Scholar links to it; it does not copy the files.
Held in Inrep Scholar's private central storage.
Held on your institution's own server, inside your self-hosted Campus application.
Infrastructure owner
Your institution — whichever storage provider you already use.
Inrep Scholar.
Your institution. Campus runs on a server you provision and control.
Repository administration
Your team manages metadata and workflow through Inrep Scholar; file-level access stays with your existing storage provider.
Managed through Inrep Scholar's central admin tools; Inrep operates the underlying storage.
Managed locally through your own Campus admin tools by your ICT or library team.
Backup responsibility
Your existing storage provider's own backup policy — outside Inrep Scholar's control.
Inrep Scholar.
Your institution. Campus ships with its own backup and restore tooling; running and retaining those backups is a local responsibility.
Domain / deployment
Runs on Inrep Scholar's shared domain; your public repository pages are hosted centrally.
Runs on Inrep Scholar's shared domain, with optional custom-domain mapping for your institution.
Runs on your own domain and server; the Campus application is installed there directly.
Migration support
Metadata mapping for records already described elsewhere; files are linked, not moved.
Metadata and file migration into Inrep Scholar storage.
Metadata and file migration into your own Campus deployment, plus server setup support.
Update responsibility
Handled centrally by Inrep Scholar — nothing for your team to install.
Handled centrally by Inrep Scholar.
Delivered to your server through Campus's own signed-release updater; your team confirms and runs the update locally.
Technical requirements
None beyond a web browser — no server to provision.
None beyond a web browser — no server to provision.
A server meeting Campus's PHP/MySQL requirements, provisioned and maintained by your institution.
Best fit
Institutions that already store files somewhere and want governed metadata, review, and discovery on top.
Institutions that want Inrep Scholar to also hold and back up the files, without running their own server.
Institutions that require research files to remain on infrastructure the institution physically controls.
Support model
Standard implementation support.
Standard implementation support, plus storage operations.
Standard implementation support, plus install and update guidance for your ICT team.
Migration & rollout
Structured migration and rollout support, on any tier
Optional deployment services that work alongside any tier without changing your ownership model.
Repository data migration — Map and transfer legacy metadata and eligible files.
Every institution's student population, storage volume, integration and support needs are different, so we prepare a tailored quote instead of a fixed rate. Tell us what you need through the request-setup form and we'll send a proposal.
Do students pay to use the platform?
No. Institutions subscribe and pay for their repository; individual students, researchers and staff are never redirected into a payment flow.
Which tier is highest, and what does it add?
InRep Campus is the highest tier. It provides a dedicated university-hosted repository application, federation with central discovery, signed licensing, deployment controls, and priority implementation support.
Which plans support monthly billing?
Campus supports monthly or yearly terms. Connect and Cloud remain annual plans and can be purchased for one to five years.
Where are files stored under each tier?
Connect retains files in the systems you already operate. Cloud stores them in Inrep Scholar's private storage, with a protected viewer. Campus stores them only on your own university server.
What happens if a subscription is not renewed?
Before a subscription lapses, the institution is reminded ahead of the renewal date.
InRep Campus: the local repository enters a read-only safety mode — public access, administrator login, backups, exports, and renewal remain available; uploads, publishing, sync, updates, and new credentials stop until renewal.
InRep Connect / InRep Cloud: the institution's own copy of its data is never affected — a lapsed subscription affects central discovery indexing, updates, and support, not data ownership.
Can Cloud data move to Campus?
Yes. Campus includes a controlled migration workflow so eligible central records and files can be imported into the university-hosted application.
Choose the repository ownership model your institution can sustain.
Start with the tier, billing term, migration scope, and deployment responsibilities made explicit.
