Qeet Group
We question, We explore,We envision, We transform.
Four words, one name. One organisation, one identity layer, one design foundation — and a portfolio of products that compose each other rather than compete for the same desk.
- 15
- Products
- 4
- Available today
- 4
- In development
- 7
- Planned
What Qeet Group is
Most software companiesbuild a product. We arebuilding the ground itstands on.
Qeet Group is one technology organisation, not a collection of separate ventures. Its products are built by different teams for different problems, but they share an identity layer, a design foundation, and a set of standards that do not bend per product.
That shared ground is the actual work. It is why signing in once reaches everything, why every interface behaves the same way, and why adding the next product costs less than the last one did.
One way intoProducts include Qeet ID, Qeetrix, Qeet Logs, Qeet Notify, Qeet Pay, Qeet People, Qeet AI, Qeet News, Qeet Mail, Qeet Calendar, Qeet Contacts, Qeet Tasks, Qeet Drive, Qeet Chat, Qeet Meet
01The ecosystem
15 products. Two dependencies.
Almost nothing in this portfolio stands alone. Every product authenticates through the same identity layer and is built from the same design foundation — so they compose rather than merely coexist.
Qeet ID
The single secure front door to everything an organisation runs.
Every product depends on this
Explore Qeet IDEvery product below signs in through Qeet ID and is built from Qeetrix.
- Qeet IDAvailableThe single secure front door to everything an organisation runs.Every product depends on this
- QeetrixAvailableThe design foundation that makes an entire portfolio feel like one organisation.Every product depends on this
- Qeet LogsAvailableOperational visibility that respects the privacy of the people in the data.
- Qeet NotifyAvailableOne way to send everything an organisation needs to send, across every channel.
- Qeet PayIn developmentPayments, billing and compliant invoicing built for how business is actually done in India.
- Qeet PeopleIn developmentHuman resources, attendance and statutory payroll, built for Indian employment.
- Qeet AIIn developmentThe layer that lets software reason over what an organisation already knows.
- Qeet NewsIn developmentA news platform where every claim carries its source and every story shows more than one side.
- Qeet MailPlannedEmail for organisations, administered alongside everything else.
- Qeet CalendarPlannedScheduling that knows who people are and what they can see.
- Qeet ContactsPlannedA single, shared record of the people and organisations you work with.
- Qeet TasksPlannedWork tracking for teams that would rather not run a project tool.
- Qeet DrivePlannedShared storage where access is governed rather than assumed.
- Qeet ChatPlannedTeam messaging that is searchable, governed and retained deliberately.
- Qeet MeetPlannedVideo meetings connected to the record of the work.
02 — Identity
Everything startsat the same door.
A person signs in once and reaches everything they are entitled to reach. An administrator grants access in one place and revokes it in one place. When someone joins, the right things open on their first day; when they leave, they close on their last — everywhere, at once.
That is only possible because every product asks the same system who someone is. It is the least visible decision in the portfolio and the one that constrains all the others.
03Technology
What the portfolio is made of.
Nine capabilities, built once and shared. Each is delivered by products in the portfolio rather than described in the abstract.
04 — Intelligence
The hard part wasnever the model.
Every organisation adopting artificial intelligence meets the same problem in the same order. The capability is easy to obtain and easy to demonstrate. Connecting it safely to the organisation’s own information is the hard part — and the only part that produces value past the demonstration.
A system that cannot see what the organisation knows is a novelty. One that can see all of it, regardless of who is asking, is a serious liability. The useful position is the narrow one between those, and reaching it depends entirely on knowing who is asking.
05Engineering and security
Principles, not badges.
Qeet Group holds no security certifications today, and this page will not imply otherwise. What it can state is the baseline every product is built to — and where that falls short of a formal attestation, the honest word is 'yet'.
- Least privilege
- Access is granted narrowly and explicitly. Nothing is permitted because it was convenient at the time.
- Secure by default
- The safe configuration is the one you get without asking. Making something less strict is a deliberate act with a name attached.
- Tenant isolation
- One customer's data is separated from another's by the architecture, not by the correctness of a query someone wrote on a Friday.
- Zero implicit trust
- Being inside the network is not a credential. Every request establishes who is asking and what they may do.
- Auditability
- Consequential actions are recorded so they can be produced later — and so that alteration is detectable rather than assumed away.
- Defence in depth
- No single control is load-bearing. Anything important is protected more than once, because controls fail.
06Scale
What actually exists.
Counts derived from the portfolio itself rather than stated — so this section cannot drift from what the site contains.
- Products
- 15
- Available today
- 4
- In development
- 4
- Planned
- 7
Across the portfolio
Running in production
Building now
Specified, not yet built
- Repositories
- 67
- Identity layer
- 1
- Design foundation
- 1
The engineering surface behind the portfolio
Every product authenticates the same way
Every interface is built from it
Organisation figures verified August 28, 2026 against the Qeet Group repository records.
08Insights
What we think, written down.
07 — Company
Progress beginswith the rightquestion.
Qeet is an acronym before it is a name: question, explore, envision, transform. It describes an order of operations, and the first step is the one most organisations skip.
It also has consequences we would rather live with than talk around. It is why the organisation keeps a register of the places its own documentation disagrees with its code, and why a roadmap entry is not allowed to be cited here as a shipped capability.
Where to next