Filtering on our servers, not on the device
Four ways to use Navōn
The same platform and the same filter underneath. What changes is who sets the standards, who they cover, and who gets to see what happened.
Schools
One policy, every student account
For a school or yeshiva setting rules on behalf of other people's children.
- Set the standards once; every student account inherits them
- Classes, assignments and teacher visibility
- Staff see what was asked and what was declined
Families
Rules that follow the child, not the device
For parents who want their children to learn AI on terms they have set.
- Your own blocked subjects, hours and daily limits
- Your rules layer on top of the school's, stricter wins
- A weekly account of what your child actually did
Individuals
An assistant that stays inside your boundaries
For one person who wants capable AI without the parts they would rather not meet.
- Chat, images, voice and video in one place
- Filtering tied to your account, on every device
- Nothing to install and nothing to switch off
Teams
The same standards across an organisation
For a business or organisation whose staff should all be working to one line.
- One filter policy for everybody on the account
- Shared projects, tasks and team workspaces
- Add and remove people as staff change
Side by side
Everything else — the tools, the models, the filter itself — is the same in all four.
| Schools | Families | Individuals | Teams | |
|---|---|---|---|---|
| Who sets the rules | The school | The parent | You | The account owner |
| Who the rules cover | Every student account | Each child you add | Your own account | Everyone on the team |
| Who can see the activity | Teachers and staff | The parent | Only you | Team administrators |
| Filtering runs | On our servers | On our servers | On our servers | On our servers |
Not sure which one fits?
Tell us how many people it is for and what you need it to refuse. We will say which of the four we would put you on, and what it costs.