by TitansBuilt on SPACE

The whole academy.In one space.

Students, faculty, research and administration in one workspace. ACADEMY connects your student records, learning platforms, finance and research computing with governed AI agents — and can become the system your institution runs on, at the pace you choose.

01 / 06Systems

Student records, learning, finance and admissions connect into one workspace, through the interfaces they already have.

Students. Systems. Intelligence. Connected.

The academic estate

Dozens of systems.One institution.

A student sees one institution. Behind the counter there are separate systems for admissions, records, tuition, learning, exams, research computing and reporting — and people carrying data between them by hand. ACADEMY brings them into one workspace: first by connecting what you have, then by taking over what should have been one system all along.

CompareEvery connection is a project. Every question is a spreadsheet.

Admissions CRM
Student records
Tuition & finance
Learning platform
Exams
Timetabling
Research computing
Reporting & BI
Spreadsheets
Email

Why now

Demand is already here. Structure is not.

Students and staff adopted AI faster than institutions could organise around it, and the compute to support them is often on campus already, waiting in a queue.

95%of full-time undergraduates in a 2026 national survey use AI in at least one form.HEPI, Student Generative AI Survey 2026
32%of administrators report an institution-wide AI policy.Tyton Partners, Time for Class 2026
50%of jobs on a 319-GPU university research cluster averaged under 5% GPU utilization.Sheinberg, Gupta & Li, 2026 (preprint)

Figures as published by the cited sources. They describe the surveyed populations, not every institution.

Live demoDemonstration environment · Fictional institution · Sample data

See it working.Not a screenshot.

A full demonstration workspace of a fictional college: cockpit, student records, admissions, exams, collection, Moodle, integrations and the agents module, all running on sample data. Open an agent, follow a request, approve an action.

academy.titans.global/demo Live demo
Loading the workspace

The workspace plays by itself. Click inside to take over.

01 / 04ACADEMY

Core

The academic record. From first inquiry to alumni.

Academy Core holds the life of your institution in one connected record: applicants, students, programs, courses, grades, tuition, staff and alumni. Run it beside your current student system through live integrations, or let it take over admissions, registration, exams and tuition module by module, when you decide.

The full footprint

The whole academic year. One system.

Core is designed to cover the yearly cycle of an institution, in the terms your offices already use: from planning the year and recruiting candidates to exams, collection, the dean of students and alumni. Adopt the areas you need first; the rest are ready when you are.

  • 01Before the semester opens

    Planning the year

    • Annual course catalogue, carried forward from last year
    • Teaching assignments and the workload plan
    • Employment letters with multi-level approval
    • Automatic timetabling from lecturer and room constraints
    • Rooms, labs and resources by type and capacity
    • Syllabi managed and published from one place
  • 02From first lead to accepted

    Prospects and applicants

    • Leads from every channel, de-duplicated and assigned to an advisor
    • Campaigns, open days and advisor calendars
    • Admission-chance simulation on a candidate’s record
    • Online application with fee payment and an electronic file
    • Decision runs against admission terms, with exceptions sent to committees
    • Acceptance letters, deposits and conversion to student
  • 03Students, courses and staff

    Running the semester

    • Student record, tracks and study plans
    • Course registration, individual or by cohort, with prerequisites
    • Exemptions, attendance lists and mid-term grades
    • Study confirmations and official documents on demand
    • Timetable changes pushed to students and lecturers
    • Lecturer records, office hours and teaching load
  • 04Exams, grades and progression

    Closing the semester

    • Exam periods, sittings and hall allocation
    • Proctor pool with automatic proctor assignment
    • Extra time and other accommodations applied to each exam
    • Final grades, weighting and transcripts
    • Second and special sittings, appeals and re-marking
    • Degree audit, progression and graduation eligibility
  • 05The financial relationship with each student

    Tuition and collection

    • Price lists, agreements and indexation methods
    • Standing orders, cards, vouchers and the cash desk
    • Sponsors, funding bodies and loans
    • Balance calculation with scholarships applied
    • Automatic holds by debt, per document and service
    • Receipts, invoices and postings to accounting and payroll
  • 06Support, aid and housing

    Dean of students

    • Scholarship tables, applications and committees
    • Eligibility checks and control of duplicate entitlements
    • Support centre for students with special needs
    • Personal accommodations that follow the student into exams
    • Dormitory placement and contracts
    • Welfare requests and follow-up
  • 07The relationship after the degree

    Alumni and career

    • A record for each degree, for graduates of several
    • Alumni mailings, events and continuing education
    • Career centre with employer accounts and job postings
    • Placement tracking and employment guidance
    • Diplomas, ceremonies and verifiable digital credentials
    • Transcripts and confirmations on request
  • 08Programs with rules of their own

    Specialised tracks

    • Continuing education and certificate studies, run as a separate entity
    • Practical-engineering tracks with project management and authority interfaces
    • Teacher training with ministry reporting
    • Health professions with clinical placements
    • Reporting packs for regulators and national statistics
    • Budget against actual by department and lecturer
  • 09Requests that run themselves

    Processes and self-service

    • Student portal, mobile app and campus kiosk
    • General requests routed to the right office and tracked to an answer
    • Appeals, special sittings and exemptions as configured processes
    • Forms and survey builder, including teaching evaluations
    • Course bidding and online registration windows
    • Management dashboards and a report builder

Module scope and sequence are defined as part of your implementation.

Example workspaceChoose a view

ACADEMYCore · Registrar cockpitIllustrative interface · Sample data

ADMISSIONS / CURRENT CYCLE

Every applicant. The next step in view.

1,284Open applications
212Awaiting documents
37Ready for decision
Activity trend12 sample points
IDSubjectNext step
APP-2041B.Sc. Computer ScienceInterview slot proposed
APP-2042M.A. EducationDocuments missing
APP-2043LL.B.Ready for decision
Connected context · Decision point

Applicant 2041 meets the admission terms. The admissions agent proposed two interview slots and updated the CRM.

  1. 01

    CRMInquiry & application

  2. 02

    COREAdmission & registration

  3. 03

    ERPTuition account

  4. 04

    LMSCourse access

Follow a studentIllustrative flow · Sample data

One student.Nine moments. One record.

From the first question on your website to the alumni network. At every moment, see which systems are involved, which agent helps and where a person decides.

ACADEMYCore · Student lifecycle
CRMCoreERPLMSIdentityPaymentsKnowledgeCalendarCredentials

01 / 09 · Inquiry

A question at 23:40. An answer at 23:41.

Maya asks about the data science program on your website. The admissions agent answers from the program catalogue, checks her eligibility and opens a lead with the conversation attached.

Agent
Admissions advisor
A person decides
An advisor follows up in the morning
crm lead.create · source: web chat · program: data-science

02 / 04ACADEMY

Agents

A digital staff. With real authority, and clear limits.

Academy Agents take defined roles across admissions, the registrar, student services, teaching operations and research computing. They read and write in your systems through scoped permissions, ask a person before sensitive steps and leave a record of every action.

Example workspaceSelect a role to see its authority

ACADEMYAgents · Role and authorityIllustrative interface · Sample data

01 / 08 · ACADEMY Agents

Admissions advisor

Answers applicants around the clock, qualifies them and keeps every lead moving.

Reads

Program catalogue, admission terms, applicant file

Writes

Leads, call bookings, document requests

Asks a personBefore any admission decision

Works in
CRMCoreCalendarWhatsApp

ChannelsWhere people ask

WhatsAppStudents
Student portalWeb & app
EmailStaff & students
Learning platformIn the course

ACADEMYAgent layer

IdentitySSO · role · scope
AgentRegistrar assistant
PolicyWhat this role may do
Human reviewApproval queue
ActionReads and writes with scoped credentials
KnowledgeRegulations · procedures
AuditEvery step recorded

SystemsWhere it acts

CoreStudent record
Learning platformMoodle · LMS
ERPTuition account
Service deskTickets

Follow a requestIllustrative flow · Sample data

“Why can’t I see Linear Algebra in my courses?”

It is 23:40 and the office is closed. The message arrives on WhatsApp and reaches the registrar assistant, with the conversation history.

channel whatsapp › agent: registrar-assistant · 23:40

03 / 04ACADEMY

Studio

Your faculty. Your module.

Every faculty works differently. Academy Studio, powered by Space Code, is the development environment where your developers, data teams and Titans FDE engineers turn a faculty’s process into a module: screens, rules, agents and automation on the shared record. Built once, governed centrally, owned by the people who run the process.

Powered byCode

Module exampleteaching-assignment.module

ACADEMYStudio · Development workspaceIllustrative interface · Sample data
// A faculty process, on the shared recordmodule teaching_assignment {  trigger semester.planning.opened  context courses + staff.availability + rooms  rules   faculty.regulations  agent   { propose assignment; explain conflicts }  review  department.head  output  timetable -> core, lms, calendar}
  1. 1Read courses, staff and rooms
  2. 2Apply the faculty’s rules
  3. 3Propose an assignment and explain conflicts
  4. 4Send to the department head for review
Module previewTeaching assignment · Screens · Rules · Agent · Permissions

A manual process. A reusable module.


As each faculty wishes

One foundation. Every faculty’s way of working.

The record, the permissions, the agents and the integrations are shared. What each faculty builds on top is its own.

01

Lab safety certification

Access to labs follows completed training, automatically.

02

Capstone matching

Students, supervisors and industry projects matched by preference and capacity.

03

Course GPU environments

A ready environment for every student, opened from the course page.

Shared by all
RecordPermissionsAgentsIntegrationsAudit

04 / 04ACADEMY

Compute

Campus GPUs. Working for every lab and every class.

Academy Compute, powered by Zenix, turns the servers and GPUs you own into workspaces people open in a browser. A course gets identical environments for a whole cohort, a research group gets its quota and idle capacity returns to the pool. The same infrastructure runs your institution’s own AI models, so student and research data stay on campus.

Powered byZenix

Example workspaceChoose who needs compute

ACADEMYCompute · GPU poolIllustrative interface · Sample data
32 GPUs · Illustrative pool
  • This profile
  • Other workloads
  • Idle, flagged
  • Free
–Allocated
–Idle, flagged
–Free

ZENIX / WORKSPACE PROFILE

Deep Learning 101 · 40 students

Image
Gold image · PyTorch course v3
Resources
4 vCPU · 16 GB · shared GPU slice
Access
Browser · campus SSO
Policy
Sessions end after class; work is saved
A lecturer and students in a computer lab, each laptop showing the same engineering environment

01 / 02

A whole class. Ready to work.

The challenge
An academic lab needs consistent environments for a new student cohort.
At work
The compute administrator defines a group, a gold image, a quota and permissions. Participants enter through the browser while IT monitors health and usage.
What changes
Requests follow the same profile, and the administrator can track allocations throughout the course.
A researcher in a lab beside a robotic arm, with a server rack in the background

02 / 02

Give research room to compute.

The challenge
Teams need access to expensive resources but have different periods of demand.
At work
Define quotas and profiles, inspect allocations and utilization and review resources flagged as idle. The workload owner agrees to the reclamation policy.
What changes
Allocation and reclamation decisions use both usage and ownership, accounting for long-running jobs in the background.

Illustrative scenarios and imagery.


Local AI

The task shapes the model. Your campus hosts it.

Open-weight model families, from compact models to reasoning, code and vision. Run them on CPU for focused tasks or on GPU for advanced workloads, and connect external APIs only where your policy allows.

Start with the servers you have.

Compact models for classification, extraction and focused assistance. Validate memory, quality and response time on your hardware.

Gemma · Phi

Combine flexibility and acceleration.

Split inference between processor and accelerator with supported runtimes. Match model size and memory to your environment.

Quantization · Hybrid runtimes

Scale to a whole campus.

Larger models, vision workloads and many concurrent users on GPU servers or a suitably sized cluster.

Qwen · Gemma · DeepSeek

QwenDeepSeekLlamaGemmaMistralPhiGraniteNemotron OllamavLLMHugging FaceNVIDIAIntelAMD OpenAI APIAnthropic APIGoogle Gemini API

Version, licence and capacity are selected as part of your implementation. External API services follow your institution’s policy.

The platform

One academy.Every role.

A cockpit for leadership, a workspace for every office and a foundation for developers. Each role sees the same record through the view it needs.

ACADEMYMy AcademyInteractive product tour

01 / 08 · ACADEMY / Leadership

From enrollment to budget, in one view.

Admissions funnel, retention risk, collection, research activity and compute use, with the context behind each number and an owner for each exception.

  • Objectives
  • Exceptions
  • Next decisions
Product tour · Example workspaceIllustrative interface

Cockpit & BI

Ask the institution a question.

The cockpit brings the measures leadership follows into one view and answers questions in plain language, with the sources attached. The same governed data feeds the BI tools your analysts already use.

ACADEMYCockpit · Leadership viewIllustrative interface · Sample data

Admissions funnel · current cycle

  • Applications4,860
  • Admitted2,140
  • Enrolled1,512
  • Retained, year 191%
Feeds the tools your analysts use
  • Power BI
  • Tableau
  • Qlik
  • SQL & open formats

Ask the data

Answer

Three programs are below 80% of target with four weeks left: M.A. Education, B.A. Philosophy and M.Sc. Materials. Education has 61 complete applications awaiting a decision.

SourcesCoreCRM

Shared context & integrations

Your existing systems.A new centre of gravity.

ACADEMY connects student systems, learning platforms, finance, identity and research infrastructure into one academic context. Information is linked to the right people, rules and permissions, so agents and modules work with what your institution already knows.

Shared academic contextThe same student. The same course. One context across every office.

Student
Course
Program
Staff
CONTEXT · RULES · PERMISSIONS
Student system
LMS
ERP
CRM
BI

Integration ecosystem

The academic stack. One space.

From learning platforms and student systems to ERP, BI, identity and research computing. FDE teams tailor each connection to your processes, permissions and environment, using the standards your systems already speak.

  • MoodleLMS
  • CanvasLMS
  • BlackboardLMS
  • Open edXLEARNING
  • Google ClassroomLMS
  • ZoomVIDEO
  • PanoptoVIDEO
  • KalturaVIDEO
  • TomaXEXAMS
  • Ex Libris AlmaLIBRARY
  • PriorityERP · CRM
  • SAPERP
  • OracleERP
  • Microsoft Dynamics 365ERP · CRM
  • SalesforceCRM
  • HubSpotCRM
  • Power BIBI
  • TableauBI
  • QlikBI
  • SnowflakeDATA
  • DatabricksDATA
  • PostgreSQLDATABASE
  • ElasticsearchDATA
  • Microsoft Entra IDIDENTITY
  • OktaIDENTITY
  • KeycloakIDENTITY
  • WhatsAppMESSAGING
  • Microsoft TeamsCOLLABORATION
  • SlackCOLLABORATION
  • Google WorkspaceCOLLABORATION
  • OutlookEMAIL
  • NVIDIAGPU
  • KubernetesORCHESTRATION
  • SlurmORCHESTRATION
  • JupyterNOTEBOOKS
  • PyTorchML
  • Hugging FaceMODELS
  • OllamaMODEL RUNTIME
  • MLflowML
  • GitHubDEVELOPMENT
  • GitLabDEVELOPMENT
  • DockerDEVELOPMENT
  • VMwareVIRTUALIZATION
  • ProxmoxVIRTUALIZATION
  • OpenStackCLOUD
  • MakeAUTOMATION
  • n8nAUTOMATION
  • ZapierAUTOMATION
  • JiraSERVICE DESK

Integration starts with your academic processApplications · APIs · Data sources · MCP · Custom integrations

Standards and protocols
LTI 1.3 · LTI AdvantageOneRoster 1.2xAPIOpen Badges 3.0CLR 2.0SAML 2.0OpenID ConnectSCIM 2.0eduGAINREST · ODataWebhooksMCPSFTP · CSV

Bring your automation into the flow: Make and n8n workflows connect to ACADEMY agents and modules through APIs and webhooks.

Self-hosted n8n can be configured for internal deployments

Product names and logos belong to their respective owners and indicate interoperability only. Integration scope is defined as part of your implementation.

The transition path

Step into the system you have.Then move past it.

Replacing an academic system in a single move is a risk few institutions should take. ACADEMY starts beside what you run today and takes over one module at a time, with both systems in step until you switch. At every phase the record stays yours, in open formats.

ACADEMYTransition · Module by moduleIllustrative interface · Sample data

Phase 0 / 4

Separate systems. People in between.

Each module lives in its own system, and staff carry data between them.

  • Current system
  • In parallel
  • ACADEMY
Module
Current systemIn parallelACADEMY
Admissions & CRMNew
Connected
Student portal & appNew
Connected
Timetabling & roomsNew
Connected
Registration & enrollmentNew
Connected
Exams & gradesNew
Connected
Tuition & aidNew
Connected
AgentsNew
Connected
Faculty modulesNew
Connected
GPU workspacesNew
Connected

Your pace

No single cutover. Each module moves when its numbers match in parallel.

Your data

The record lives in open, documented structures you can query, export and take with you.

Your roadmap

New needs become modules in Studio, not requests in a vendor’s queue.

The foundation is ACADEMY. The institution is yours.

Aidome™AI control plane

Every agent. Every model.Under your rules.

Student data is among the most sensitive an institution holds. Aidome governs how AI touches it: a self-hosted control plane between ACADEMY’s agents and modules and every model and tool they reach. On-premises, private cloud or air-gapped.

What you gain

Six controls. One operating boundary.

Every AI interaction on campus passes through a shared layer of access, security, policy and operations before it reaches a model or a record.

01

One gateway. Every model.

A single OpenAI-compatible endpoint across open, local and hosted models. Change a route, not your modules.

In ACADEMY: model choice across CPU, GPU and hosted APIs becomes a policy, not a rebuild.

02

Protection at the prompt.

Prompts and responses are inspected and filtered in real time, with PII masking and data-loss prevention.

In ACADEMY: agents work with student records while identifiers and grades stay inside your environment.

03

Agents with defined authority.

MCP servers and tools are governed in one framework: which capability is available to which agent.

In ACADEMY: a service agent can open a ticket. It cannot change a grade.

04

Identity that carries through.

Scoped, revocable virtual keys per application, team and user, with SSO / SAML and role-based access.

In ACADEMY: the roles and review points of each office are enforced at the model boundary.

05

Spend you can plan.

Budgets, quotas and rate limits per key, team and user. Caching and cost-aware routing reduce paid tokens.

In ACADEMY: see AI cost per faculty, course and agent, and send routine work to capacity you already own.

06

Evidence, ready when asked.

Audit logs, usage analytics and automated compliance reporting for security, operations and risk teams.

In ACADEMY: a decision trail from a student’s question to the model that answered and the person who approved.

Decisions on admission, assessment and progression stay with people. Agents prepare, explain and record, with the oversight and logging that regulation increasingly expects of AI in education.

How agents ask for approval
Self-hostedDockerOn-premisesPrivate cloudAir-gappedMulti-region

Aidome™ is a product of Aidome. Capabilities as published at aidome.co. Availability and scope are defined as part of your implementation.

Deployment & adoption

On your ground.At your pace.

Run ACADEMY on your own servers, in a private cloud or as a hybrid of both, matched to your data, permissions and performance requirements. Start with one process, put it to work with the team that owns it and expand from there, supported by Titans FDE engineers.

On-premisesPrivate cloudHybridAir-gappedMulti-campus
  1. 01

    Embed — Start where the work happens.

    Sit with the office that owns the process. Choose a first high-value process, such as teaching assignment or registration requests, and map the people, rules and systems behind it.

    A first process
  2. 02

    Connect — Bring the campus together.

    Connect the student system, the learning platform, the ERP and identity. Give the process the context and tools it needs.

    A connected workspace
  3. 03

    Activate — Put the first module to work.

    Configure the module, define the agent’s role and its approval points. Work alongside the team until it is part of the daily routine.

    A working module
  4. 04

    Expand — Build on what is connected.

    Extend to another office, faculty or module. Reuse the integrations, context and governance already in place.

    Compounding capability

Built around your institution

Across the campus.Around the way you work.

From recruitment and registration to teaching, research and finance. One foundation of record, knowledge, permissions and agents, with processes shaped around each office.

Admissions & recruitment

From first question to enrolled student.

Answer applicants at any hour, keep every lead moving and give the committee one complete file. The CRM stays current without anyone typing.

CRMAgentsCore

Q&A

A clearer pathto implementation.

What is ACADEMY?

ACADEMY is Titans’ platform for higher education, built on SPACE. It connects the academic record, learning platforms, finance and research computing in one workspace, with governed agents, a development studio for faculty modules and GPU workspaces powered by Zenix.

Does ACADEMY replace our student information system?

It can, and it does not have to. ACADEMY starts as a workspace over your current systems, reading and writing through their interfaces. When you are ready, Core takes over one module at a time, running in parallel until the numbers match.

Does it work with Moodle and other learning platforms?

Yes. ACADEMY connects to learning platforms through their web services and through LTI Advantage, synchronises enrolments and grades and lets agents handle course operations within the permissions you define. Course assistants can run on models hosted on your own infrastructure.

Can agents write to our systems, or only read?

Both. Each agent has scoped credentials that define what it may read and write. Sensitive actions, such as releasing a hold or changing a status, wait for a person’s approval, and every step is recorded.

Where is student data processed?

Where you decide. ACADEMY can run on your servers, in a private cloud or as a hybrid. Open models can run on your own CPU and GPU, so prompts and records do not have to leave the campus.

Which languages do agents and interfaces support?

Interfaces and agents work in multiple languages, including right-to-left languages, and can answer each person in the language they write in. Interfaces are designed to WCAG AA accessibility. Quality in each language is validated during implementation.

How does each faculty adapt it?

In Academy Studio. Developers, data teams and FDE engineers build faculty modules on the shared record: screens, rules, agents and automation. The foundation stays common; the way of working is the faculty’s own.

What about our ERP and BI tools?

ACADEMY connects to ERP systems for tuition, budgets and procurement, and feeds the BI tools your analysts already use. The cockpit adds a leadership view and plain-language questions on the same governed data.

Do we need GPUs to start?

Not for every use case. Compact models and focused tasks can run on CPU. For teaching labs, research and larger models, Academy Compute manages the GPUs you have and helps plan the capacity you need.

How do we start?

With one process that matters, such as teaching assignment or registration requests. Together we map it, connect the relevant systems and put a first module to work with the team that owns it.

Can we see the system working?

Yes. The live demo on this page is a full demonstration workspace with sample data from a fictional college. A guided session on your own processes follows with the Titans team.

Your next academic year starts here

Your institution.Ready for what’s next.

Your systems. Your regulations. A space that grows with your institution.