Question 1

Who creates the 3D map?

Accepted Answer

The map is generated from your existing plans, evacuation plans, surveys, then refined by the Loupe team. You adjust it afterwards in the editor: moving a shelf doesn't require an architect.

Question 2

In which languages?

Accepted Answer

Seven today: French, German, English, Italian, Spanish, Dutch and Luxembourgish. The public interface follows the visitor's language, and AI-assisted translation speeds up the work while leaving you editorial control.

Question 3

What about accessibility?

Accepted Answer

It is part of the design: keyboard navigation, screen-reader compatibility, careful contrast, semantic HTML, following the WCAG rules behind public-sector requirements (RGAA in France, Swiss federal standards). Interactive 3D plans are the current exception, as our accessibility statement explains.

Question 4

Can we test it on our own catalogue?

Accepted Answer

Yes. The demo can run on your real catalogue, and a test access lets you evaluate Loupe with your own data before committing, with no risk to your system.

Question 5

Does it work on mobile?

Accepted Answer

Yes. Loupe is 100% web and mobile-first: your visitors reach it from their phone, with nothing to install.

Question 6

How does Loupe compare to StackMap or SpringShare?

Accepted Answer

They are good tools, each covering part of the need: StackMap adds shelf-level wayfinding to the catalogue, and the SpringShare suite (LibCal, LibGuides) covers bookings and subject guides. Loupe brings these uses together on one platform, a 3D map of the building, the catalogue in natural language, bookings, events, guides, with a single front door for the visitor, seven languages, and a hosting and processing scope documented for each deployment.

Question 7

Do we have to change our ILS?

Accepted Answer

No. Your ILS remains the source of your catalogue. Available connectors, required access and the connection scope are checked with your team before deployment.

Question 8

Does Loupe replace our OPAC or website?

Accepted Answer

No. Loupe sits on top of your ILS and reads your data where it is. On the public side it's your call: Loupe can become your website, or slot into your existing one as a simple widget. Your OPAC stays available.

Question 9

What if we change ILS later?

Accepted Answer

No problem. Loupe connects to your ILS through open standards and is tied to no vendor. The day you migrate, your public layer, map, catalogue, bookings, events, doesn't move: we reconnect the new system. You lose neither your user experience nor your investment in Loupe.

Question 10

Where is the data hosted?

Accepted Answer

The platform is hosted in Switzerland, and so is Loupe's AI by default. The exact hosting and processing scope is documented for every deployment.

Question 11

How much does it cost?

Accepted Answer

Free is free with 4 staff accounts and 2 GB. Basic costs CHF 349 excluding tax per month, billed annually. Map, Loupe Search, Affluence and custom configurations are quoted separately.

Question 12

Are we paying for things we won't use?

Accepted Answer

Free and Basic are two starting configurations. You can add modules or request a custom setup; scope and pricing are agreed before commitment.

Question 13

Is it compatible with public procurement?

Accepted Answer

Yes. Loupe is billed as a fixed subscription, set by contract and multi-year if needed, with no usage-based billing or variable tokens. The model is built for public tenders.

Question 14

How long does it take to get started?

Accepted Answer

Loupe prepares the connection, checks the flows and documents what each team needs to do.

Question 15

Which libraries do you already work with?

Accepted Answer

Loupe equips academic and public libraries in Switzerland. On request, we put you in touch with institutions comparable to yours.

Frequently asked questions

Product and use cases

Integration

AI and data

Pricing and contract

Deployment

Your visitors no longer have to look for the right door.