Run it on your own fleet before you buy it
A pilot puts UserAuthGuard in your own Google Workspace at no cost, from the day you connect Google Admin through to the start of your next school year. You assign real devices to real students, Google enforces it at the sign-in screen, and you decide at the end whether it stays. Pilots start on a rolling basis, so there is no application window to miss.
Apply for a pilot Book a 20-minute walkthrough firstThe full product, your data, the founder on call
A pilot is not a sandbox with sample devices. It is your Chromebooks, your students and your OUs, with enforcement turned on where you say so.
Enforcement on your real devices
Each Chromebook gets its own organizational unit carrying a sign-in restriction that names the allowed student. Google refuses anyone else before a session starts. You pick the buildings or grades it applies to.
Direct line to the people who build it
Setup, bulk assignment and the first loaner and lost-device cases are done with us on a call, not from a help article. What your techs ask for shapes what gets built next.
No cost and no obligation
Nothing is invoiced during the pilot and there is no contract to exit. If it does not earn its place by the end, the enforcement OUs are removed and you keep the free read-only view.
From first sync to the first day of next school year
The calendar is yours, not ours. A pilot that starts in January and one that starts in May follow the same five steps and both end at the start of your next school year.
-
1
To start
Connect and see
A Google Workspace super-admin signs in and UserAuthGuard reads every device, user and OU. You see the fleet as it is, including the devices no student is accountable for, before anything is changed.
-
2
Next
Assign and enforce
We bulk-assign devices to students from your SIS export or your spreadsheet, agree the scope, and turn on enforcement. Spares and loaners get their own states from day one.
-
3
The school year
Run it every day
Techs handle swaps, repairs, loaners and lost or stolen devices in UserAuthGuard, and Google keeps the sign-in screen in step with each change.
-
4
End of year
Collect and reconcile
Device return and end-of-year collection run through the same records, so what was handed out and what came back is one list, not two.
-
5
Before next year
Decide
You have a full year of your own records to judge it on. Keep it, at the per-student price on the pricing page, or step back to the free read-only view.
What we ask of you, and what you can ask of us
We ask
- A Google Workspace super-admin to connect the account and approve the enforcement scopes.
- A student-to-device list, or a willingness to build one with us from what Google already knows.
- One tech who uses it daily and tells us plainly what is wrong with it.
- A short check-in call about once a month.
You can ask
- For enforcement to start with one building or one grade and widen only when you say so.
- For the data processing agreement and FERPA and COPPA documentation before the first sync. See compliance.
- For enforcement to be removed at any point, with your OUs left as we found them.
- To read how the two districts already running it use it day to day, in the case studies.
Tell us about your fleet
We read every application ourselves and reply by email. If a pilot is not the right fit, we say so and suggest the free read-only view or a walkthrough instead.
Pilots are for districts in Pennsylvania and New Jersey, where we can be on site. UserAuthGuard is running today at Union City Public Schools (13,000+ active Chromebooks) and Southeast Delco School District (6,943 Chromebooks).
Founder, Asan Digital LLC, Montgomery County, Pennsylvania. stef@asan.digital or (267) 639-8522, Monday to Friday, 8am to 5pm ET.
Application received
Thanks, . We will read it and reply to with next steps, or with an honest no if a pilot is not the right fit.
In the meantime, the free read-only view works for any district, pilot or not.
Start free