You’re exploring the full DataBridge platform free, with synthetic Future Horizons University data. Everything is unlocked; actions run in your demo session (in-session only, not saved to a real backend).

FHU Databridge
Enterprise
Pricing
Integration

System profiles

Per-source-system profile packs: entities, codesets and rule packs.

sits-native
Production
Tribal SITS
Full SITS entity map, canonical field catalogue and the F01–F13 rule families including the 8 legacy-scar rules.
TargetTribal SITS (Oracle / e:Vision)
Quality rules69 audit rules · F01–F13
Package@databridge/profile-sits
banner-native
Production
Ellucian Banner
Banner canonical profile — SPRIDEN, STVMAJR, STVCAMP, SHRTGPA plus the SGBSTDN/SORLCUR programme registration tables used by Banner↔SITS migrations.
TargetEllucian Banner (Oracle / Ethos)
Package@databridge/profile-banner
workday-native
Production
Workday Student
Workday Student entity map and field catalogue for the canonical model, sourced from Workday Reports-as-a-Service.
TargetWorkday Student (RaaS)
Package@databridge/profile-workday
hesa-tdp
Production
HESA Data Futures
Statutory return target profile — entities, fields, codings and rules for the HESA Data Futures collection from 2024/25 onward.
TargetHESA Data Platform (C25061+)
Package@databridge/profile-hesa-tdp
salesforce-edu
Production
Salesforce Education Cloud
Maps Contact, Account, Affiliation, Program Enrollment and Course Connection objects onto the canonical student model.
TargetSalesforce Education Cloud
Package@databridge/profile-salesforce-edu
dynamics365-edu
Production
Dynamics 365 Education
Profile for Dynamics 365 Education entities — Contact, Account, Student, Programme and Course Enrolment.
TargetMicrosoft Dynamics 365 Education
Package@databridge/profile-dynamics365-edu
techone-financeone
Production
TechnologyOne Finance One
Finance ledger, cost-centre and transaction profile for TechnologyOne Finance One — used by the HESA Finance return mapper.
TargetTechnologyOne Finance One
Package@databridge/profile-techone-financeone
How profiles relate to adapters
A profile is the canonical model of a source system — entities, fields, codesets and the rule pack used to audit data quality. An adapter is the canonical connector — the transport that pulls rows out of the source. Adapters and profiles ship as separate packages so you can swap transports (Oracle vs REST vs file) without changing the profile, and so the same profile drives audits across institutions.