Explore a demo or start your own trial.
Just looking? Try edSI Demo College with published administrator and staff logins. Each browser gets its own sample session; no signup is required. When you want your own college workspace, start with four details:
- Enter your college name and a contact email at signup.
- Choose a trial username and a password of at least 12 characters.
- Save the recovery code shown once. Open your sample workspace.
College ownership and staff/student identities are verified during implementation. Your trial account administers only the workspace it created.
Start a college trialTry an ordinary college day.
- Open a sample student and review tuition, installments and preparation checks.
- Review programs, cohorts, instructor profiles and class schedules.
- Explore attendance, placements, supplier bills and cash forecasting.
- Ask the records assistant about sample balances or placement readiness.
- Open the migration preview and load the fictional CSV example.
Reset sample data at any time after confirming the college name. Use invented data while exploring; uploads of documents and real staff invitations are held until institutional setup.
AI helps prepare. Your college approves.
The intended workflow combines AI suggestions with deterministic validation and explicit college review. AI will propose configuration and mappings from approved source material. It will not invent approved program requirements, change financial balances, merge uncertain identities or grant roles on its own.
- 01Implementation phase
Discover your college
Your team identifies the source systems, programs, cohorts, fee schedules and records in scope. Prepare a small anonymized export and name a college data owner. AI will help summarize the source structure and suggest configuration questions.
- 02Implementation phase
Propose mappings & configuration
AI will suggest how source columns match edSI fields, identify program and cohort candidates, and draft a configuration plan. Each suggestion should include its source, rationale and confidence. Uncertain matches go to a review queue; approved requirements and fee rules come from your college.
- 03Implementation phase
Review data quality
The planned workflow will flag missing values, inconsistent dates and possible duplicates. Your team confirms corrections and merges. Names and email matches are suggestions, not permission to merge identities or grant account access.
- 04Implementation phase
Dry run in staging
An approved source snapshot will be transformed into a separate staging dataset. Review source-to-target IDs, rejected rows, relationships, document links, student counts, balances and payment totals. A dry run does not update production.
- 05Implementation phase
Approve & import
Your data owner approves the mapping version, exception list, reconciliation report, access roles and cutover window. The planned importer will use stable source identifiers and a batch ledger to avoid duplicate imports. Credentials stay in secure server configuration.
- 06Implementation phase
Reconcile, launch & monitor
Compare the imported records and totals with the approved source snapshot. Pilot one administrator, one staff member and one student. Retain a pre-import backup and batch rollback plan, obtain college sign-off, then enable any separately approved ongoing synchronization.
Before processing real records with an AI provider, agree the permitted data fields, model/provider settings, retention terms, regional requirements and human review process. Treat imported text as source data rather than instructions to the agent. Keep credentials and unrelated sensitive documents out of prompts.
Clear the trial before your real college data.
Choose Start production setup in the workspace. Review the removal notice and type your college name. edSI replaces the trial with an empty institution workspace and removes the old sample records, trial edits, example accounts, configuration and trial activity.
Your college name, reserved address and trial administrator account remain so you can continue preparation. Programs and cohorts start empty, and the financial opening balance is unconfigured. This action cannot be undone and does not start billing or activate production.
What to bring to the first review.
| Owner | Prepare |
|---|---|
| College administrator | College name, intended address, data owner, implementation contact and approved role roster. |
| Academic team | Programs, cohorts, approved delivery requirements, class schedules and requirement references. |
| Finance team | Fee schedules, opening balances, payment history, outstanding amounts and reconciliation totals as of an agreed date. |
| IT / source owner | Source systems, field dictionary, stable record IDs, anonymized export, tenant details and a scoped access plan. |
| edSI implementation | Review scope; propose mappings and configuration; implement and test authorized connections; prepare staging, reconciliation and rollback reports for approval. |
Clear before you begin.
Can we try edSI without creating an account?
Yes. Open demo.edsi.app to use published administrator and staff demo logins. Each visitor gets a separate fictional sample session for up to four hours, with role switching and a fresh-demo option. Staff access excludes financial and administrative records; uploads and account changes are disabled. Create your own college trial when you want a longer-lived workspace.
Do we need a ChatGPT or Microsoft account to try edSI?
No. New college trials use a username and password chosen at signup. Microsoft tenant configuration is a later implementation step. The original DataWiz pilot retains its existing sign-in route.
What can we explore?
The trial includes fictional students, tuition installments, recorded payments, programs, cohorts, instructor qualification examples, class schedules, labs, placements and a sample supplier bill. You can change sample records and ask the records assistant about them. The assistant currently uses rules over permitted records; it is not a live generative AI service.
Can we upload real student records during a trial?
Use invented data in the trial. Document uploads and real staff invitations are disabled for temporary accounts. The CSV preview runs locally in your browser; its contents are not sent to the server or an AI provider. Production data access and imports follow verified institutional identity and review.
How do we return to our trial?
Open edsi.app/login and enter your trial username and password. Sessions last up to seven days; sign in again when required. Keep the recovery code shown at account creation. Email password resets are not enabled.
What if we lose the password?
Use the recovery-code option on the trial sign-in page to set a new password. Recovery replaces the code and signs out previous sessions. Without the password or recovery code, automated account recovery is unavailable; you can create a new sample trial. A contact email alone cannot recover access.
Can we restore the sample data?
Yes. Choose Reset sample data in your workspace, review the warning and confirm the college name. This discards trial record changes and restores the fictional examples. It cannot be undone.
What happens when we choose production setup?
After your confirmation, edSI removes this trial’s dataset and creates a new empty implementation workspace. Students, payments, bills, vendors, staff examples, programs, cohorts, settings and trial activity are cleared. Your college name, reserved address and administrator trial login remain. Re-enter reviewed production configuration rather than carrying trial settings forward.
Does starting production setup immediately launch the college?
No. Temporary credentials can prepare programs, cohorts and connection metadata in the clean workspace. They cannot add student, financial or personnel records there. Microsoft identity, approved account linking and the migration/import implementation must be completed and tested before live operation.
Will AI migrate everything automatically today?
AI-assisted mapping, live source connectors and import execution are planned and are not enabled in this release. Today you can explore sample workflows, preview CSV fields and duplicates locally, and prepare connection metadata. The approach below defines the review and reconciliation gates for the implementation.
What will our college need to provide?
A source-system contact, a data owner, an anonymized sample export, approved programs and requirements, field definitions, migration scope, role roster and expected record/financial totals. At production activation, an authorized administrator supplies tenant consent or scoped source access through a secure connection process. Do not place passwords or client secrets in documents or metadata fields.
How do college subdomains work?
Choose an optional address at signup or accept an automatically generated one. A working trial link is available immediately on edsi.app. Your college subdomain is reserved and becomes active after hosting and certificate verification; the reserved name alone does not activate DNS or grant access.
Does the trial start billing or send real messages?
No card is collected and no subscription starts automatically. Reminder tools create drafts only, and sample financial actions record examples without moving money. Commercial terms, support and migration scope will be agreed before paid activation.
Explore your sample college.
No card or external account setup. Your implementation decisions can wait until you have explored.
Create my trial