Security
Your M3 data goes to your M3.
Loupe is a desktop app that talks to Infor M3 through its own APIs, as the person using it. Here is exactly what goes where, so your security team does not have to guess.
How Loupe reaches M3
Direct to M3
M3 API calls go from the desktop app straight to your ION API gateway. They do not pass through Beredo servers, and we cannot see which tables you open or which transactions you run.
Signed in as you
Every person signs in to M3 with their own M3 user through Infor's sign in. M3 security decides what each of them can read and change in Loupe, exactly as it does in M3.
Nothing new to govern
No service account, no second copy of your M3 roles, no data warehouse on the side. Take someone's rights away in M3 and they are gone in Loupe too.
What Loupe stores, and where
Loupe keeps your work, not your M3 data. Configuration is saved to your organisation so it can be shared. Everything you fetch from M3 stays on the machine that fetched it.
Saved to your Loupe organisation
- Your work. Saved compares, automations and API collections: the tables, filters, steps and field mappings, with their revision history and sharing settings.
- Your team. Members, invitations and roles.
- Your environments. The ION API registration files your admins upload to connect each M3 environment.
Kept on your machine
- M3 data. Table rows, transaction results, compare results and exports.
- Imports. Spreadsheets you load into an automation.
- History. Run logs, response history, field history and your open Explore tabs.
- Saved passwords. Encrypted with your operating system keychain, and never synced anywhere.
Access, the way admins expect it
One licence covers every user, so the question is never who can afford a seat, only who should have access to what.
- Sign in with Microsoft. People sign in to Loupe with their Microsoft work account.
- Three roles. Admins manage the organisation, users build and run, and viewers get read only access to what is shared with them.
- Per person environments. Admins choose which M3 environments each person can use.
- Per person tools. Switch Compare, Automate, Explore, Run and Code on or off for each person.
- Guardrails on changes. Automations only run in the environments they allow, and ask for confirmation before changing data.
Loupe Code and AI
Loupe Code is the one part of Loupe that uses a cloud service, because it uses AI to write code. Here is what that involves.
Metadata, not records
To build against your M3, Loupe Code looks up definitions: programs, transactions, fields, tables, columns and custom fields. These read only lookups run through a Beredo service, with a fixed set of queries. They never write to M3.
The AI holds no keys
The AI that writes the code never receives an M3 credential and cannot reach your systems. What it learns about your M3 comes back from those metadata lookups, and it is sent to Anthropic's models to generate the code.
Isolated per customer
Each customer's builds run in their own isolated workspace, and your environment connections are encrypted per customer and shared with no one.
You decide what ships
Loupe Code deploys nothing by itself. You see the plan, preview the result on your own machine, and choose what to install in M3. The source is yours to review and keep in your own git repository.
Security questions
- Can Beredo see our M3 data?
- No. The desktop app calls your ION API gateway directly, so the tables you open and the transactions you run never pass through Beredo servers.
- Does Loupe use a service account?
- No. Environments are added from an Infor web application registration, and every person signs in to M3 as themselves. Backend service account files are rejected.
- Where are imported spreadsheets kept?
- On your machine. Rows you import into an automation are held in the desktop app while it runs. Only the automation itself, its steps and field mappings, is saved to your organisation.
- Does Loupe Code deploy anything to M3 by itself?
- No. Loupe Code produces source and packages. You preview them on your own machine and decide what to install, where and when.
Need more for a security review, a questionnaire or a data processing agreement? Write to hello@loupeapp.net.
See it on your own M3.
Bring an environment and we will show you Compare, Automate, Explore and Code on your own data.