Vuisio has been building a responsible company from the start, pragmatically: describing what actually exists rather than displaying commitments our size cannot yet honour. This page separates what is in place, what is under way and what remains an objective.
Last updated:
Vuisio, published by Geezot
How to read this page
In place True today, verifiable.
Under way Started, not finished.
Objective Planned, no date promised.
01
Our vision
Four convictions guide our decisions. They are not slogans: each one translates into concrete technical and economic choices, verifiable in the product.
Technology should respect the people using it
A professional tool should not make tracking the price of admission. Vuisio works without measuring how its users behave, because that is not needed to hold a meeting.
Data is not a commodity
Our revenue comes from subscriptions and nothing else. Nothing is resold, nothing is passed to a third party, and no advertising model will ever make that promise expensive to keep.
Performance forces no ethical compromise
Our SFU, written in Rust, routes media without transcoding: less computation for the same service. Technical frugality and respect for users point the same way; they are not in tension.
Decisions are made for the long run
The core is published under AGPL 3.0 and Vuisio can be self-hosted. Our customers therefore do not depend on how our company fares to keep using the product.
02
Environmental
We have not carried out a carbon assessment and we claim no neutrality. Here is what is true today, and what we want to measure before saying anything more.
Current status
In place
An essentially software business: no industrial production, no vehicle fleet, no heavy physical infrastructure of our own.
Little business travel: most of the work happens remotely, and video conferencing is our daily tool.
Frugal by design: the SFU routes media without transcoding, the most computationally expensive operation in video conferencing.
No superfluous processing on our sites: no analytics, no tracker, no third-party CDN. Fonts are served by us. Every request avoided is a resource saved.
Self-hosting is possible: customers can run Vuisio on servers already in service rather than adding capacity.
Infrastructure hosted in France and sized on real need, with no comfort headroom.
Future objectives
Objective
Measure before announcing
Establish a first real measurement of our footprint, starting with the consumption of our infrastructure, rather than publishing an unverifiable estimate.
Under way
Optimise cloud resources
Track how our servers are actually used, cut unused capacity and improve throughput per connected participant.
Objective
Favour responsible suppliers
Bring environmental criteria into the choice of our hosts and providers, alongside sovereignty and security.
Objective
Publish indicators over time
Track and then publish environmental indicators here, once the company has the size and the history that make them meaningful.
03
Social
Vuisio is a young company. What follows describes how the project actually works, not procedures our size does not yet justify.
Respect for users
The free plan is not a crippled product designed to force an upgrade: meetings are unlimited in length and in participants. Respecting users starts with not trapping them.
Accessibility
We aim for an interface that is legible, well contrasted and usable by keyboard. Vuisio has not yet been audited against RGAA or WCAG: that is an open task, not an achievement.
Privacy
No meeting data is used for anything other than the service. Privacy is covered in detail in the governance section of this page.
Security
Encrypted streams, a media core written in Rust, third-party browser dependencies kept to the strict minimum. Security protects the people in the meeting first.
Company culture
A small team, code published as open source, and technical choices exposed publicly. What can be checked from outside forces consistency inside.
Diversity
Vuisio recruits and collaborates on the basis of skills and motivation. None of the following criteria plays any part, in either direction:
Gender
Origin
Age
Disability
Religion
Sexual orientation
We have no formal diversity policy, nor the headcount that would make statistics meaningful. Inclusion has been part of the project's culture from the start: that is what we will formalise as the team grows, not a document we would publish before it means anything.
Wellbeing
Respect for the team
A sustainable workload and protected personal time. A young company asks for commitment; it does not justify burnout.
Transparent communication
Decisions are explained, including the unwelcome ones. Nobody learns about an important change after the fact.
Continuous improvement
Internal feedback is taken seriously and acted on. What is not working is named, then fixed.
04
Governance
Vuisio is published by Geezot. Governance today is that of a young structure: few people, quick decisions and clearly identified responsibility. We would rather say so than describe committees that do not exist.
Responsible governance
Decisions commit us for the long run: we avoid those that would make the product depend on a single supplier, or on a business model at odds with our promises.
Transparent decisions
Structural technical choices are visible in the published code. Changes to product policy are announced, not slipped into an update.
Sustainable product development
AGPL 3.0 licence, self-hosting available, documented formats and APIs: nobody is locked into Vuisio, technically or contractually.
Privacy
In place
Minimisation: we collect only what the service needs. A meeting requires no account at all.
No tracking: no third-party analytics, no advertising cookie, no external CDN on our pages. The anti-spam protection on our forms runs without any third-party service.
No resale: data is never sold, never transferred, never used for advertising.
Location: our servers are hosted in France, beyond the reach of extraterritorial legislation.
Control: self-hosting lets you entrust us with no data at all.
Security
Under way
Security by design: a media core written in Rust, a memory-safe language, and an attack surface reduced by the absence of third-party dependencies in the browser.
Encrypted streams between participants and the infrastructure.
Verifiability: the SFU, the web client, the installer and the load-testing tool are published under AGPL 3.0. Our claims can be audited line by line.
Continuous improvement: dependency tracking, patches and updates are part of the development cycle.
Compliance
Under way
The GDPR is a founding design goal, not compliance bolted on afterwards: data minimisation, explicit purpose, hosting within the European Union.
We follow the European regulatory framework applicable to our activity and fold it into the product as it evolves.
Meeting streams and their hosting stay in France, therefore outside the scope of extraterritorial legislation such as the Cloud Act. Signing in to the portal through an American identity provider does send the email address through a company that is subject to it: that is a choice left to the user, and signing in with a password avoids it entirely.
05
Our ESG roadmap
Two columns, one rule: on the left what is true today, on the right what is not yet.
Today
A digital company, with no industrial infrastructure
Privacy by design: no tracking, minimised data
Transparency: core software open under AGPL 3.0, claims that can be checked
Responsible development: technical frugality, hosting in France
Next steps
Define ESG indicators suited to our size
Write down a formal ESG policy
Set up environmental monitoring of our infrastructure
Structure continuous improvement through regular reviews
Publish an annual ESG report
None of these steps carries a date. We would rather announce what we ship than promise a schedule a young company does not control.
06
A commitment to transparency
This page is not a frozen marketing document: it describes a state, at a date, the one shown at the top. It will change as Vuisio does.
As the company grows, our commitments will be documented, measured and published. What appears today as an objective will in time become an observed, dated fact. And if an objective is dropped, it will be removed with the same candour rather than left in the window.
We would rather have a short, accurate page than a thick, unverifiable report. It is the best sign of seriousness we can offer at this stage.
Are you evaluating Vuisio for your organisation?
Tender, due diligence, supplier onboarding: we answer your ESG questions precisely, including on what we cannot do yet.
We would like to know which pages are read, using our own tool, hosted in France. One cookie, six months, no identifier this page's code can read, nothing sent to a third party. Refusing writes nothing at all: no cookie, and no row in our records.
03
Social
Vuisio is a young company. What follows describes how the project actually works, not procedures our size does not yet justify.
Respect for users
The free plan is not a crippled product designed to force an upgrade: meetings are unlimited in length and in participants. Respecting users starts with not trapping them.
Accessibility
We aim for an interface that is legible, well contrasted and usable by keyboard. Vuisio has not yet been audited against RGAA or WCAG: that is an open task, not an achievement.
Privacy
No meeting data is used for anything other than the service. Privacy is covered in detail in the governance section of this page.
Security
Encrypted streams, a media core written in Rust, third-party browser dependencies kept to the strict minimum. Security protects the people in the meeting first.
Company culture
A small team, code published as open source, and technical choices exposed publicly. What can be checked from outside forces consistency inside.
Diversity
Vuisio recruits and collaborates on the basis of skills and motivation. None of the following criteria plays any part, in either direction:
We have no formal diversity policy, nor the headcount that would make statistics meaningful. Inclusion has been part of the project's culture from the start: that is what we will formalise as the team grows, not a document we would publish before it means anything.
Wellbeing
Respect for the team
A sustainable workload and protected personal time. A young company asks for commitment; it does not justify burnout.
Transparent communication
Decisions are explained, including the unwelcome ones. Nobody learns about an important change after the fact.
Continuous improvement
Internal feedback is taken seriously and acted on. What is not working is named, then fixed.