CampusWay.Less time managing university software.
Your university has a dozen systems. You should not have to operate every one of them.
CampusWay is a browser extension from Gravitas Technologies. Ask for what you need in plain English, right inside your university's pages, and it opens, reads or prepares it using workflows that people have reviewed. It does the clicking. It never presses the final button for you.
- 97
- campus workflows, recognised from thousands of different phrasings.
- 0
- AI calls on a mapped run, which finishes in about three seconds.
- 100%
- of public mapped tasks completed end to end, 57 of 57.
- 5/5
- form drafts filled and stopped before Submit.
Internal benchmarks, October 2026.
See how it works.
When you ask for something, Argus, our request router, recognises which mapped task you mean, or declines. It is our own model, trained and benchmarked: 8.4 MB, small enough to run in the browser, and it decides in 0.16 milliseconds. Every held-out request written by people that it routed went to the right workflow, and it routed none of the requests it should refuse.
The server sends back only a reference to the reviewed workflow, and the extension runs its steps in your browser in about three seconds. That is what zero AI calls means here: no reasoning model is asked anything, and Argus only picks the map. It never decides what to click.
A request without a workflow yet is handled once by a reasoning model, under a strict read-only policy. Nomos, in training, turns successful runs like that into draft workflows. It proposes; people review and approve. University portals change, pages move and processes break, so Talos, also in training, oversees every run and pauses, stops or retries an alternative when a step breaks.
People review every workflow before it runs, so a mapped task takes the same path every time, with nothing improvised. Each new workflow is one more kind of request that never needs a reasoning model.
Animated illustration on a generic university portal. A student types "open my degree audit". Argus, our request router, recognises it in 0.16 milliseconds, and the extension runs a reviewed workflow in three steps with zero AI calls. A second request with no workflow yet goes to a reasoning model once, under a read-only policy, and is held for review; Nomos, in training, proposes a draft workflow from that run for people to approve, so the next identical request needs no reasoning. When a page changes, Talos, in training, retries an alternative route, and escalates if that fails.
Running today: reviewed workflows and a read-only reasoning fallback.Trained and benchmarked: Argus, the request router.In training: Nomos draft maps and Talos run supervision.Illustration.
University software without the busywork.
CampusWay works inside the software students already use. The interface stays simple; the steps happen in the background.
Learning management systems.
See what is due today or this week, find an assignment and reach course materials in Blackboard. Academic answers are read from the page in your browser; no model is involved.
Academic administration.
Registration dates, holds, degree-audit gaps and academic records across Banner and DegreeWorks, without searching separate portals.
Campus services.
Calendars, printers, housing and service requests, from the same box you type into.
Routine forms.
Draft Mode prepares forms such as device registration and stops before the final button. Every action that needs review or approval stays yours.
Coverage grows with every workflow that is mapped, tested and reviewed. And not every task needs the same depth of help.
Ask once. It goes as far as it safely can.
Find an assignment, check a deadline, locate a form, review a course requirement. Every task CampusWay can do sits on one of four levels, and each level goes one step further than the last.
Level 0: Answer.
Reads the facts and answers.
“What is due this week?”Reads your course site and lists what is due, without leaving the page you are on.
Level 1: Navigate.
Reaches the right app or form.
“Open my degree audit.”Goes through the student portal and opens DegreeWorks for you.
Level 2: Prepare.
Fills a draft and stops before the final button.
“Register a device on campus Wi-Fi.”Asks for the details up front, fills the form and stops before Submit.
Level 3: Orchestrate.
Chains several systems into one result.
“Am I ready to register?”Checks holds, registration dates and the registration tools, then returns one checklist.
Requests with no map yet are handled under the same read-only rules, and each one becomes a candidate for the next reviewed workflow. Level two deserves a closer look, because it is where CampusWay stops on purpose.
It prepares. You submit.
Draft Mode is how CampusWay handles forms. It asks for everything it needs up front, fills the form field by field and reads each value back to confirm it landed. Then it highlights the final button and stops. The run ends as prepared, not completed: the decision and the click stay yours.
In our benchmarks, every form draft stopped before Submit: five out of five. That rule is not a setting. It is one of several.
Read-only. Draft-only. On the record.
Limits built into the product, and an audit trail for every run.
- It never submits.
- CampusWay never submits, enrolls, pays, approves or sends anything on a university system. If it is unsure whether a click is final, it treats it as final.
- Signing in stays yours.
- Passwords and multi-factor prompts are always yours. When a page asks you to sign in, CampusWay pauses and waits for you.
- What is never stored.
- Passwords, the values you type, documents and raw page snapshots.
- What stays on your device.
- Your optional profile (campus, school, level and class year) and your chat history.
- What a reasoning model sees.
- Only when no reviewed workflow exists: your request plus a redacted structure of the page.
- What is logged.
- Every request and action, so each run can be audited. Logging is required during the pilot.
A university pilot adds formal review on top: student records, security, accessibility and sign-on, set out below.
Built for students. Designed for institutions.
The student beta is free. A student-facing product is how CampusWay builds validated workflow coverage inside real university environments, one reviewed task at a time.
For the university, the same workflows can become one automation layer across your academic, administrative and financial systems, without replacing any of them. On the roadmap: department-level automation, permissioned information exchange between offices, consistent execution records and operational visibility.
Your systems stay. Nothing to replace, nothing to migrate.
Invite-only student cohorts are planned to reach about 1,000 students by spring 2027, each step gated on safety and reliability bars.
How it reaches campus.
The rollout path, in order.
- Chrome Web Store, unlisted. Invited students install from a private listing.
- Microsoft Edge. The same package, listed for Edge.
- Managed devices. University IT can force-install it on the machines it manages.
How a pilot is structured.
The review work planned for each university pilot.
- FERPA school-official agreement, covering how student records are handled.
- HECVAT Lite, the higher-education security questionnaire, for the university's security review.
- WCAG 2.1 AA self-audit and VPAT, for the accessibility review.
- Single sign-on, as cohorts grow beyond invite codes.
Questions and answers.
Something we have not covered? Email universities@gravtechnologies.com.
Does CampusWay use AI?
As little as it can. A known request is routed by Argus, our own small model, and runs from a reviewed workflow with zero calls to a reasoning model. A reasoning model steps in only when no workflow exists yet, and that run becomes the starting point for a reviewed one.
Every reviewed workflow is one less place AI is needed. Our models exist to take AI out of the loop, not to add more of it.
How does CampusWay protect student information?
Mapped tasks run from reviewed workflows bundled in the extension, and the server returns only a reference to the workflow. The safeguards listed above are the complete list.
Each university pilot is planned around a FERPA school-official agreement and a HECVAT Lite security review.
How reliable is CampusWay?
In our benchmarks, every public mapped task completed: 57 of 57, in about three seconds each, with zero AI calls.
Portals change, so reliability is an ongoing job, not a one-time test. That is the job of Talos, our run overseer, now in training: it watches each run and stops or redirects it when a page moves. Requests with no workflow yet go to a reasoning model under the same read-only rules.
Which systems does CampusWay work with?
The systems universities already run, including Banner, Blackboard, DegreeWorks and OnBase, on public pages and signed-in portals alike. Each new university is mapped, tested and reviewed before its students are invited.
What is setup like?
About four clicks: pick your university, accept the pilot notice, and you are enrolled. An optional profile (campus, school, level and class year) tailors answers such as registration dates, and it stays on your device.
Is CampusWay free for students?
Yes, the student beta is free. Institutional licensing is a separate offering for universities.
When will CampusWay be available?
Invite-only student cohorts come first, and they grow as each safety and reliability bar is cleared. Join the waitlist to hear when a cohort opens at your university.
Your university has enough software.
CampusWay does the clicking. You make the decisions.
Students. Join the waitlist and we will tell you when a cohort opens at your university.
Universities. We are taking pilot inquiries now. Tell us about your campus, your workflows and your requirements for integrations, security, deployment and licensing, or email universities@gravtechnologies.com.