About
About Intenv
Intenv is an independent knowledge base about intelligent environments — the technology of physical spaces that can sense, reason about and respond to the people in them.
The field goes by many names — ambient intelligence, ubiquitous computing, pervasive computing, the Internet of Things — and it turns up at every scale, from a single connected room to a smart building to a whole city. That breadth makes it genuinely interesting and, for a newcomer, genuinely confusing. Intenv exists to make it legible: to explain the concepts, the systems and the standards in plain language, and to be honest about where the trade-offs lie.
What we cover
Six through-lines organise everything here: smart homes, ambient intelligence, the Internet of Things, smart buildings, smart cities, and ambient assisted living. Each topic collects guides that go deeper, and a glossary defines the vocabulary you meet along the way.
How it is written
Guides are written for curious non-specialists — people evaluating a technology, studying the field, or simply trying to understand a device in their home. We aim for accuracy over hype, we explain acronyms the first time they appear, and we try to describe the downsides as carefully as the benefits. Where a term or standard is contested or still settling, we say so rather than pretending otherwise.
What Intenv is not
Intenv is an editorial reference, not an organisation. It is not affiliated with, endorsed by, or connected to any conference, professional association, standards body, university or vendor, and it does not represent any of them. Product, protocol and technology names are used for identification and description only; they remain the property of their respective owners. Nothing here is a substitute for professional, medical, legal or financial advice, and coverage of a product is never an endorsement.
Corrections
Technology moves, and reference material has to move with it. If something here is out of date or wrong, we would rather know — guides are revised as standards evolve, and each carries the date it was last updated.