Everything it does
Not a highlights reel. This is the whole of it, grouped by what you are trying to do — so you can check for the one thing you actually came to find out about. Every one of them has a page explaining what it does and what it will not do.
94 things, across 11 parts
Meetings
Everything you would expect of a video meeting, and the controls you only miss when a meeting goes wrong.
Video meetings
Camera, microphone and screen for everybody in the room, running on our own servers rather than somebody else’s.
Meetings that stay inside your bandwidth
Each person’s browser subscribes only to the speaker and the tiles actually on screen, at the smallest quality that still looks right; everybody else is dropped rather than hidden.
One link, a code, or a calendar entry
A meeting is a link somebody sends, a nine-character code somebody reads out, or an entry that arrives in a calendar on its own.
People with no account
A host opens the meeting to guests, copies a link, and closes it again — from inside the room, without leaving the people waiting outside.
Waiting room, lock, and who may in
Knock and admit, lock the room, restrict by email domain, set a passcode, and decide whether people may arrive before the host.
How people arrive
Muted or not, camera on or off, who may unmute, who may share, who may chat — set per meeting and enforced on the server rather than in the interface.
Private mode
One meeting, end-to-end encrypted, which visibly switches off recording, captions and the recap — and says which, before you press it rather than after.
Breakout rooms
Split the room into groups and bring them back.
Chat, with files
Messages in the meeting, with attachments up to 10 MB that are scanned for viruses before anybody can reach them.
Hands and reactions
Raise a hand, and react without interrupting.
Moderator controls
Mute everybody, mute one person, remove somebody, lock the door.
A run-of-show the whole room can see
Items with times, a countdown every screen computes for itself, and a pause that actually moves the clock.
Moving a meeting
Change the date, time, length or zone and it stays the same meeting — same link, same code, same people — with everybody told and the old time struck through.
Repeating meetings
Daily, weekly or monthly, created once.
Checks that tell you which thing is wrong
Is my microphone dead, am I echoing, is my camera frozen, is my input too hot, can they actually hear me — each answered separately instead of one "check your settings".
Devices, backgrounds and appearance
Pick a microphone, camera and speaker before you join; blur or replace what is behind you; choose how the room looks to you.
Who has been talking
A quiet measure of how the speaking is spread across the room.
“Come to the meeting”
Pull somebody who is signed in but elsewhere into a meeting that is already running.
Inviting people by email from the room
Up to fifty individual invitations from inside a live meeting, so nobody sees anybody else’s address.
The room on a phone browser
A meeting works in a phone browser with nothing installed — the link you were sent is the whole of it.
Presenting and working together
A whiteboard, documents, live web pages, a code and science workspace, polls, tests and eight more ways to put something in front of everybody.
Sharing a screen
A window, a tab or a whole display, with the room laid out beside it or above it.
Drawing on what is shared
Anybody the host allows can draw on the shared screen, on top of whatever is there.
Handing over control of your screen
Somebody else clicks and types on your machine, not just points at it. No browser can do this — it is what the desktop app is for.
A whiteboard the room shares
Draw together, with everybody seeing the same board, and a late arrival getting the whole of it rather than the part they were present for.
A document on every screen
A PDF or a slide deck presented to the room, on the same page for everybody, driven by the host.
A web page or a built site, presented
An .html file, a zip of a site, or a URL put on the stage and driven by the host — sandboxed so it cannot reach anything of ours.
The Lab
A code, maths, physics and chemistry workspace on the stage that the room edits together. Python, JavaScript and HTML run in the browser, in a sandbox, so nothing executes on our servers.
The lesson library
22 written lesson packs across coding, maths, physics and chemistry, plus whatever an organisation writes for itself — and every cover is the lesson itself rendered, never an illustration.
Polls
A question on every screen, tallied for the host, and shown to the room only when the host decides to.
Tests
Six kinds of question — multiple choice, select-all, true/false, matching, ordering and written — with a clock, auto-hand-in, and marking.
Flashcards
A deck made from the meeting, to practise with afterwards.
The idea wall
Everybody puts something up at once, and the wall groups what came back into themes.
The muddiest point
Ask the room what did not land, anonymously, and get the answers grouped rather than as a list of ninety notes.
Buzzer
First hand down wins, visibly, for the whole room.
Pick somebody at random
A wheel the whole room watches land on the same name at the same moment — and the server picks, so nobody can rig it.
Questions
A queue of questions from the room that the host works through.
Handing something to the room
Put a file or a link in front of everybody at once.
Real mathematics everywhere a person writes
Proper typeset maths and chemistry in chat, polls, tests, flashcards, the idea wall, recaps, emails and lessons — not a picture of an equation.
AI
Captions while it runs; a transcript, minutes and a recap afterwards. On our own servers, priced openly, and switchable off.
Live captions
Speech written on screen as it happens, recognised on our own servers rather than sent to anybody else’s.
Captions you can actually read
Size, position and weight set per person, per browser, with a live sample while you choose.
A searchable transcript
The words of the meeting, kept only when the host asks for them, and searchable afterwards — so "when did we agree that" is a search rather than an afternoon.
Minutes, written and emailed
Minutes written from the transcript a few minutes after the meeting ends, and sent out without anybody asking.
A recap with decisions and actions
Summary, decisions and action items on the meeting page — each one checked back against the transcript rather than asserted.
“Where are we?”
A read of where the room has actually got to, on demand, from what has been said.
Help in the Lab
“Explain this error” and “Give me a hint” beside somebody’s own code — a hint, deliberately, rather than the answer.
Writing a test, a deck or an exercise
A test, a flashcard deck or a Lab exercise written from what the meeting covered, for a host to review before anybody sits it.
What the AI costs, in the room
A live figure for what this meeting has spent, a catalogue of what each feature costs measured rather than estimated, and one switch that stops all of it including the jobs that run after the meeting.
AI that can be turned off entirely
Per organisation and per meeting. Nothing is sent anywhere, and the features that depend on it disappear rather than failing.
Recording and broadcast
Record it, stream it, or direct it like a programme — with everything that was on screen actually in the file.
Recording
A meeting records itself into a real video file, drawn with our own layout rather than a stock one.
Recordings that include what was on the stage
The presented document, the whiteboard, the Lab and the idea wall are drawn into the recording, not just the cameras and the shared screen.
Watching it back
Recordings play in the browser and in the phone app, without downloading a copy.
Streaming out
A meeting streamed live to YouTube or anywhere that takes RTMP.
The Studio
A broadcast director inside the meeting: scenes, virtual sets, a green room, talkback to a presenter, face effects, audience overlays, and a vertical cut for phones — one renderer shared by the room, the recording and the stream.
Clips
Short pieces cut out of what was recorded.
Recordings that never go missing
A failed upload keeps the file, retries itself hourly, and shows up on a page somebody can see rather than being discovered a month later.
Attendance
Who was there and for how long, judged by your own rule, sent back to the system that asked for the meeting.
A register nobody takes
Every meeting produces who was there and for how long, down to the minute they joined and the minute they left.
Present, late or absent — by your rule
The organisation sets what late means and what counts as attending, and the arithmetic is printed beside every verdict rather than hidden inside it.
It goes back where it came from
Attendance exports, and is pushed back automatically into the system that asked for the meeting.
A camera at a door
A camera pointed at a place, a list of enrolled faces, and a ledger of who came in and who went out — recognition on our own servers, consent recorded, every threshold a setting.
A camera on its own device
Open a link on a Raspberry Pi or a spare phone and it watches a space with nobody signed in — shown once, revocable, and able to do exactly one thing.
Rosters that stay in step
People arrive from the system your organisation already runs and stay in sync, so nobody maintains a second list.
Calls and messages
A number and a handle for everybody, calls that ring wherever they are, and messages nobody else can read.
Everybody gets a number and a handle
Given automatically on the day an account is made, changeable twice in a lifetime, and never reissued once retired.
Calling somebody directly
Ring a person rather than scheduling a meeting with them. The ring reaches them on any page they have open and on their phone.
Calls nobody else can hear
A personal call is end-to-end encrypted between the two people on it.
Messages
Conversations and groups with pictures and voice notes, searchable, and encrypted end to end.
Who is allowed to reach you
A contacts wall, quiet hours, and a meeting that refuses calls on your behalf and records that it did.
Moments
A picture or a short video for one person, which goes when they have seen it — off unless the organisation turns it on, never between staff and a member, and sealed at rest.
The apps
Desktop, Android, and a browser that needs nothing installed at all.
The desktop app
Windows, macOS and Linux, with the one thing no browser can do: letting somebody take control of your screen. Updates itself.
The Android app
Calls, messages, meetings, tests, recordings and your account, in a pocket — with calls that ring on the lock screen like a phone call.
The iPhone app
The same, on iPhone.
Keeping it on a home screen
The website installs to a phone or desktop home screen and behaves like an app, with no store involved.
Being told a meeting is starting
A notification ten minutes before, and again when the host actually starts it.
Running an organisation
Roles, sign-on, billing, branding, safeguarding and an audit log — the half of a platform nobody demos and everybody needs.
One organisation can never see another’s data
Enforced by the database itself, not by remembering to write the right query — a mistake fails closed instead of leaking.
Single sign-on
People arrive already signed in from the system your organisation already runs, with nobody keeping another password.
Who may do what
Owner, administrator, host and member, with the difference enforced everywhere rather than only in the menus.
Two-step sign-in
A second factor, required of the people who run the place.
Forgotten passwords, done properly
A reset that actually signs the old sessions out rather than leaving whoever had the password still signed in.
It looks like yours
Your logo on the way in, and your own backdrop behind everybody in the meeting.
A calendar, and a feed
Month, week, day and agenda views, a file for one meeting, and a subscribable feed that keeps a phone’s own calendar up to date.
Plans, trials and what you have used
Plans, a trial that ends by itself, metering, a wallet, and card payment.
A log of what was done
Every moderation action, role change and integration change, with who did it, in a log the database itself refuses to let anybody edit.
Safeguarding
A named officer, a reporting route, and access that is recorded every time it is used.
Reports
What happened across the organisation, rather than one meeting at a time.
What you are storing
How much has been kept, per organisation, and where it is.
Mail that arrives
Invitations, reminders and minutes, with retries, a dead-letter queue somebody can see, and an unsubscribe link that works without signing in.
Integration
An API, webhooks and single sign-on, so meetings are created where your work already lives.
A real API
Create meetings, add people, read attendance and mint sign-ins from your own software — versioned, documented, and described by a machine-readable specification generated from the code that validates the requests.
Webhooks
Your system is told when a meeting starts, when it ends, when attendance is final and when a recording is ready — signed, retried, and dead-lettered rather than dropped.
It plugs into the system you already run
Meetings created where your work already lives, the right people already invited, and attendance sent back on its own.
It runs on our own machines, in Canada
Not resold from somebody else’s video platform. The servers are ours, in Beauharnois, Quebec.
Trust
Where it runs, who can reach it, what is measured — and the things we will not build.
Readable, in three themes
Dark, light and a frosted light theme, every colour pair measured against the accessibility standard rather than eyeballed, and nothing that means anything by colour alone.
How much of this is actually checked
Thousands of automated checks across the website, the phone app and the desktop app, plus scripts that drive the real deployment with real browsers — and a page inside the product that says in plain words what each one protects.
A browser that cannot be turned against you
A strict content policy, code from somebody’s lesson run in a sandbox that can reach nothing of ours, and uploads scanned before anybody can open them.
Modules
The parts that only some organisations want, kept out of everybody else’s way.
Everything a place that teaches needs
Seminars, rosters, attendance, tests, lessons and the integration with the system a place that teaches already runs — the deepest part of the product, because it is where it started.
A building that knows who is in it
Cameras at doors, enrolled people, and a ledger of crossings, beside the meetings.
Wondering whether it does something that is not here?
Ask. The list above is what we are confident saying in public, and it is shorter than what the product actually does.
Back to the front pageTell us what you are trying to do
We will answer with which of the above matters for it, and which of it you can ignore.
info@seeuall.com