International mobility and recognition

Every exchange counts.

ErasmusPath takes student mobility from the first learning agreement to the final recognition. It proposes course equivalences, your staff decide, and students' personal data stays on your university's servers.

Request a demo See how it works
  • Personal data stays on your servers
  • Erasmus Without Paper built in
  • Six languages

Why it's hard today

Mobility still runs on attachments, spreadsheets and goodwill.

  1. 01

    Agreements that travel by e-mail

    Learning agreements bounce between students, coordinators and partner offices as attachments. Versions multiply, signatures go missing, and nobody is sure which one counts.

  2. 02

    Recognition decided case by case

    Students come home to find a course doesn't count. Coordinators compare syllabuses by hand, every semester, for every partner.

  3. 03

    Personal data in too many places

    Transcripts and student records get copied into shared drives and outside tools, and data protection officers are left with questions nobody can answer.

The product

One place, from learning agreement to recognition.

ErasmusPath covers the whole mobility: what students choose, what coordinators approve and what finally counts towards the degree.

Product tour

See it at work.

Illustrations of real screens, filled with demo data.

Approve agreements without the e-mail chain

Coordinators see each student's plan next to the host courses, comment on it and approve it. Signatures travel to the partner over EWP.

  • Every version kept, with its signatures
  • Comments visible to the student and both coordinators
  • Status always shown as an icon plus words

Privacy by architecture

Personal data stays on your university's servers.

ErasmusPath is built in two halves. Your node runs the portal and keeps every personal record. Our EU platform does the analysis and only ever receives course data.

Your university's node

On your servers, or hosted for you in isolation

  • Student and staff accounts
  • Learning agreements and their signatures
  • Transcripts and documents
  • Grades and grade conversion rules
  • EWP exchanges with partners
  • Audit logs

What crosses

  • Degrees and subjects
  • Transcript text, redacted on your node
  • Node version and health
  • Aggregated counters

What never crosses

  • Names, ID numbers and birth dates
  • E-mail addresses and phone numbers
  • Documents and student records

ErasmusPath platform

Run by us in the EU

  • Equivalence proposals
  • Subject recommendations
  • Transcript analysis, in memory
  • The global subject catalogue
  • Licences and service status

Partner universities

Mobility data travels over Erasmus Without Paper, node to node, never through our platform.

  • Your node calls the platform; the platform never calls your node.
  • If our platform is unreachable, your node keeps working on its signed licence for up to seven days.
  • If your agreement ends, your node turns read-only: everything can still be read and exported.
Read how we protect data

Deployment

On your servers, or hosted by us.

Both options run the same signed software. Choose by who should run the servers, not by features.

Self-hosted

Run the node in your own data centre with the erasmus-node installer. It checks the server, verifies our signed images, sets up TLS, takes encrypted backups and rolls back a failed upgrade by itself.

Installing a node with erasmus-node
$ ./erasmus-node check --domain mobility.university.edu
✓ All checks passed
$ ./erasmus-node install --version 1.4.0 \
    --domain mobility.university.edu \
    --admin-email it-admin@university.edu
✓ Node installed and running
$ ./erasmus-node enroll ERAS-7K2M-9QX4-HT3P-D8VW
✓ Enrolled with the ErasmusPath platform
$ ./erasmus-node status
Mode: full

Hosted by us

No servers to spare? We run an isolated node for your university at your own address: its own database, keys, secrets and encrypted backups. If you leave, you get a full export.

Compare the options

Operations and trust

You always know how the service is doing.

  • A public status page

    Uptime for each service over 90 days, incidents with their updates, and planned maintenance. Your node shows the same.

  • Maintenance announced 72 hours ahead

    Planned work is published at least 72 hours in advance, by e-mail if you want it and in a calendar feed you can subscribe to.

  • Signed releases

    Every image is signed and ships with a software bill of materials and build provenance. The installer refuses anything it cannot verify.

  • Audit logs on both sides

    Your node records sign-ins, approvals and changes. On our side, every operator action is logged with its reason.

  • EU hosting, clear GDPR roles

    The platform runs in the EU and its AI provider keeps data in the EU. You control your students' data; when we host your node, we are your processor.

  • Designed to meet ENS

    ErasmusPath is designed to meet the requirements of Spain's National Security Framework (ENS). It is not ENS-certified.

See service status Read how we protect data

Where it comes from

Built with universities in Spain and Italy.

ErasmusPath's workflows, catalogue and recognition rules were shaped on real degree programmes in Spain and Italy, with the people who sign learning agreements every semester.

We are welcoming a first group of universities. If you want ErasmusPath to fit your office from day one, talk to us.

Ask about early access

Questions

Frequently asked questions

Does student data leave our university?

No personal data leaves your node. The platform receives course data and transcript text already redacted on your servers (no name, ID number, birth date, e-mail or phone). It processes that text in memory and stores nothing but a usage record.

Does the AI decide equivalences?

No. ErasmusPath proposes equivalences with a match score and the topics behind it. Coordinators and vice deans accept or reject each one, and the record shows who approved what.

Does it work with Erasmus Without Paper?

Yes. Learning agreements and transcripts of records are exchanged with partner universities over EWP, directly between nodes. Mobility data never goes through our platform.

Do we need our own servers?

No. You can run the node yourself with our installer, or we host an isolated node for your university. Both run the same signed software.

What happens if your platform is down?

Your node keeps working. Its licence is signed and valid for seven days, so learning agreements, approvals and EWP carry on. Only equivalence proposals, recommendations, transcript analysis and catalogue updates wait for the platform to return.

What happens if we stop using ErasmusPath?

Your node switches to read-only mode: everything can still be read and exported. If we host your node, we hand you a full encrypted export that you can restore on your own server or read with standard tools.

How are updates delivered?

As signed releases. The installer verifies every image, takes a backup, migrates the database and rolls back by itself if anything fails. Planned maintenance on our platform is announced at least 72 hours ahead.

How is ErasmusPath priced?

By institution size, with monthly quotas for the AI and catalogue features. Every plan includes the full workflow, EWP and both deployment options.

Bring your hardest exchange.

In a demo we walk through your partners, your approval steps, your data protection questions and how you would deploy.

Request a demo See pricing