Spec 001 ยท For instructors who build

What will your students try next?

Sign Up
Works withCanvasBlackboardMoodleBrightspaceMany more...

The premise

You've never just adopted a textbook.

Sure, you might start with one. But then you add the case that it should have had, the exercise your students will argue about in the hallway, or the experiential lab that levels up their learning. This is your course. You've always built it your way.

Now the tools can be yours too. Describe the thing you've always wanted your students to do. Create the idea. Design the tool. We'll build it, connect it, and keep it running.

You do your thing. We'll do the rest.

Right within the LMS

From an idea to your gradebook.

01You

Describe the tool the way you'd describe it to a sharp TA: what students do, what counts, and what you want to see.

02Voshi

The builder writes it. You get a working tool, not a mockup.

03You

Try it in the Sandbox as a student would. Change your mind; change the tool.

04You

Add it to your course from inside Canvas, Blackboard, or Moodle, like any other assignment.

05Voshi

Students launch it from the course. Scores land in your gradebook column. Nobody emails you for a link.

The division of labor

You do the one thing. We do the other 99.

You build this part

Your tool

The clever part. The part only someone who has taught the course could have thought of. Nobody else can do it, so nobody else should.

We handle this part

Everything else

  • Compliance + security
  • Procurement + review
  • Accessibility
  • Legal + privacy
  • LTI + LMS
  • Payments + commerce
  • Support + relationships
  • Campus approvals
Ready for students

Your course

Connected, approved, and supported inside the LMS your students already use.

Across the hall

Your tools in the course across the hall.

Share your tool in Voshi, and any instructor can add it to their own course. Across the hall. Across the world.

Shared in the LMS

Your tool shows as a proper "external tool" in their LMS, just like other plugins. They pick it, and it's in their course.

Run in the LMS

No links to pass around, nothing to install, no support tickets. Voshi runs the tool in their course exactly as it runs in yours.

The other 99

99requirements.
Already handled.

A tool that students launch from a course has to satisfy the university before it satisfies you: security review, accessibility, student privacy, the gradebook, procurement. Voshi has it handled.

SOC 2 TYPE IIHECVATVPAT / ACRWCAG 2.2 AAFERPAGDPRPCI COMPLIANCEPENETRATION TESTINGTAX REMITTANCEPURCHASE ORDERSGRADEBOOK BEHAVIORDATA RETENTIONVENDOR REVIEWPRIVACY TERMSREFUNDSROLE MAPPINGSINGLE SIGN-ONSECURITY REVIEW
See all 99 requirements

Questions you'd ask

Will my university allow it?

Your tool runs inside Voshi. As an existing vendor, we've gone through the university reviews and done the paperwork. We ensure every shared tool meets educational expectations and standards.

What if I'm not a programmer?

You describe; our builder writes. Try the result as a student would, and ask for changes until it's right. Most builders never open the code.

For those who do code, connect your favorite tools with our MCP.

Who owns the tool?

You do. It lives in your Voshi account and not within your university. It goes where you go.

Can a colleague use it?

Share your tool in Voshi, and they add it to their own LMS. We'll verify that it meets university accessibility and security standards.