BrightKite
No migration

We're a layer, not a platform. Your files stay yours.

BrightKite works on top of Google Docs. No file conversion, no new login, no separate platform to learn. Everything stays in Google Drive where it already lives.

Google Drive native

Student work lives in their Google Drive, fully searchable, shareable, and accessible through Google Classroom. No proprietary file format. No walled garden.

Zero migration

No data import, no file conversion, no weeks of onboarding. Teachers keep using Google Classroom exactly the way they do now. BrightKite adds a layer on top.

Trivial to cancel

If you ever stop using BrightKite, remove the lock and delete the BrightKite comments. The Google Doc is back to normal. Your data was never trapped.

No new accounts

Students sign in with their existing Google Workspace account. No new passwords, no new profile, no "accept terms" screen for 30 students on day one.

What "layer" actually means

When a teacher assigns a writing task through BrightKite, the student opens a Google Doc — their own Google Doc, in their own Drive. BrightKite adds a secure writing environment on top of that document.

The content they write goes into the Google Doc. The writing process data (keystrokes, paste events, session timing) is captured by BrightKite. The teacher sees both.

No vendor lock-in. No proprietary format. No "export your data" process needed if you decide to leave. The document was always yours.

See how it works with Google Docs

Book a 25-minute call and we'll show you the Google Drive integration in action.

Book a call