Open beta — free while in beta
An agentic butler for your home.
Every room, device, and person of your house in one living model — and an AI agent on top that watches over it, speaks to you on the channels you already use, and acts on your behalf within well-defined permissions.
The vision
Smart homes today are a patchwork of vendor apps that don’t know about each other, don’t know who lives in the house, and can’t reason. Viki unifies all of it behind a single structured model of the house — with an intelligent agent on top. It’s live now, in open beta.
Sign up with a proper account — identity handled by Ory, not a demo cookie — and a guided onboarding takes you from first login to your own house: rooms, devices, and the people who live there.
Every room, device, person, and permission in one structured, realtime model — rendered as a navigable 3D house where lights actually glow, shutters sit at their true percentage, and the sun and weather match the sky over your real address.
A per-house AI agent connected to the LLM you choose — Anthropic, any OpenAI-compatible API, or a fully local endpoint. Owners choose the brain; Viki provides the body, and every action is bounded by the permissions of the person asking.
Talk to your house in the app, on Telegram, or on WhatsApp — and let it read plain email too. Each channel carries a trust level: ones that can’t prove who’s typing get read-only or limited powers, so consequential actions stay on strongly-authenticated ground.
Time, device, and weather triggers — and camera recognition, so the gate can open when the gardener arrives. Recognition profiles exist only with the subject’s consent, and anything that opens a door or gate asks for in-app approval first.
Every house exposes a Model Context Protocol endpoint. Point Claude, your IDE, or any MCP client at it with a personal token and it can inspect rooms, read sensors, and operate devices — under your permissions, never more.
Netatmo and BTicino modules run today in sandboxed workers — bring your own vendor credentials to link them. The module SDK is open so anyone can integrate any smart-home vendor; a public module registry is coming.
Owners, family, guests, the gardener — every action is checked server-side against the person asking, on every channel. The agent can never act on someone’s behalf beyond what that person could do in the app.
Automations
Viki’s agent turns plain requests into workflows — the canonical examples from the vision, verbatim, all running today:
“Lower the shutters when it rains.”
“When you see the gardener arrive on the camera, open the gate.”
“Remind me to put chlorine in the pool when I haven’t added it for more than a week.”
Workflows are stored as inspectable, editable definitions — the agent writes them, and you can review, pause, or delete them at any time. Recognition triggers need the subject’s consent, and doors and gates always ask a person before they move.
For developers
Provider modules are small packages with a manifest and a capability-scoped API, sandboxed by the host. The full contract — lifecycle, permissions, freshness tiers — is documented in docs/MODULE_SDK.md in the repository, and modules load from a local directory today.
Devices that only speak on your LAN reach Viki through a tiny gateway you run at home. It connects outbound only — no open ports, no inbound rules — pairs with a revocable token, and relays state and commands over a single socket.
Mint personal MCP tokens from settings and hand your house to any MCP-capable client or agent. Tokens are scoped to you, enforce the same server-side permissions as the app, and can be revoked at any time.
Open core
Provider modules and their SDK are open source — device coverage grows with the community, and nothing about your hardware is locked away. The brain stays yours too: bring your own LLM key, point Viki at a self-hosted or local model, or use the managed default when it arrives.
Viki is free while in beta. Later, simple per-house plans: one plan covers the whole house and everyone in it, paid by the owner.