One company skill
Register the production skill in your account. Customers connect it to their own project.
For Loxone and Wiren Board integrators
Alice speaks on behalf of your company.
Your Alice skill, domain, and customer projects — in one admin workspace.
- Your Yandex account
- Your domain
- Separate projects
- Loxone and Wiren Board
1company skill
2controller types
4connection steps
How the service works
One skill, separate projects
Each customer connects to your skill. Your team manages projects, devices, rooms, states, and commands in the selected platform.
Separate customer projects
Each installation has its own controller, devices, rooms, states, and access boundary.
A repeatable setup
Connect the controller, map devices, test commands, and hand over the project.
Four operating models
Use SHD Project admin, a separate deployment, an API integration, or source delivery.
How it works
How the pieces fit together
The integration connects Yandex Smart Home with the projects your company delivers.
01CustomerUses Alice at home
02Yandex HomeVoice, query, action
03Your branded skillOne customer-facing integration
04Your platformProjects, mapping, states, and commands
LoxoneWiren Board
The customer uses your skill; the platform routes requests to the right project.
Inside the platform
How the team works with objects after Alice is connected
After connection, the team sees projects, discovered devices, Alice mapping, and synchronization status.
03 · Alice mapping
Map each device to Alice
Assign a room, type, and capabilities so the team can verify the customer experience in advance.
Ready for synchronization
What your team gets
A clear way to run projects
One place shows connections, devices, Alice mappings, and errors. Customers work with your company through your skill.
Your skill
The skill is registered in your company account and works under your brand.
Your customers
The relationship remains with the company that designed and delivered the smart home.
Your domain
Customers use your domain; the exact setup depends on the selected plan.
Your process
Your team repeats the same connection, testing, and handover sequence on every project.
Five ways to work
Choose how your platform will run
Choose a ready connection to SHD Home, work in SHD Project, a separate deployment under an operating license, an API integration, or source-code handover for independent development. Select the system mix separately.
Which systems are included
Select systems for pricing. In the ready connection, controllers are billed separately.
Ready SHD Home connection
₽25,000 one-time + ₽300/month per controller- SHD Home skill in the Yandex catalogue
- Ready-made project and connection structure
- No development or publication of your own skill
- Launch and maintenance by SHD
- A repeatable process for each new project
Use the ready-made SHD Home skill and SHD platform. The one-time connection fee depends on the selected platform. Controllers are billed separately at ₽300/month each.
Recommended
Workspace
SHD Project under your brand
₽69,000 one-time + ₽300/month per controller- Your company’s Yandex Smart Home skill
- Your domain and brand for customers
- Customer projects in one admin workspace
- We launch the first project together
- SHD handles servers, updates, and monitoring
SHD hosts and supports the platform. You use your own skill, domain, and brand while managing customer projects in SHD Project. The price includes white-label setup, the first project launch, standard updates, basic monitoring, and fixes for reproducible platform issues. Controllers are billed separately at ₽300/month each. Source code and self-managed deployment are not included.
Your system works with SHD
Scoped estimate, from ₽199,000 + ₽300/month per controller- SHD provides the platform, servers, and services
- Your customer-facing skill and domain
- Your system exchanges data with SHD through an API
- API, documentation, and launch agreed together
- Controllers run through SHD, while projects and settings are managed in your system
SHD provides the platform and operates the servers. You keep your skill and domain, while your system connects to SHD through an API. API scope, timing, SLA, and support are agreed separately.
Dedicated OEM — operating license
From ₽299,000 one-time- A separate platform instance without the shared workspace
- Your domain, brand, and skill
- Deployment in your infrastructure or an agreed environment
- We launch the first project with your team
- Launch configuration and instructions
The platform runs separately from SHD’s shared infrastructure. When deployed in your infrastructure, the application files remain on your server and are technically accessible to your administrators for operation. Dedicated OEM grants the right to use this instance within the agreed environment; rights to independently develop the product, replicate it to other environments, transfer it to third parties, or create derivative products are not included. Launch and basic configuration are included in the price. Updates and technical support are provided under a separate agreement.
Source code — project handover for independent development
From ₽699,000 one-time- Platform source code and repository
- Deployment configuration
- Database migrations
- Architecture and installation documentation
- Deployment team onboarding — up to 8 hours
- Your team handles deployment and support
The source code is delivered under a non-exclusive company license. Exclusive rights and resale are agreed separately. Your team deploys, updates, and supports the platform after handover; further development services and infrastructure are not included.
Controller ecosystems
Loxone and Wiren Board, one customer experience
Different controller workflows. The same company-owned layer for discovery, mapping, states, and commands.
Loxone
From Loxone Config to Alice
Discover the Miniserver project, select customer-facing devices, and synchronize states with Yandex Smart Home.
01
ConnectUse the Miniserver connection details.
02
DiscoverRead controls, states, rooms, and available capabilities.
03
SelectChoose what belongs in the customer-facing skill.
04
OperateRoute commands and keep states synchronized.
01Client Loxone Miniserver02Your platform03Your company skill
Wiren Board
MQTT without opening the customer network
An outbound agent discovers MQTT devices and routes commands without exposing the controller directly to the internet.
01
AgentRun the connector inside the customer installation.
02
InventoryDiscover MQTT topics, devices, and available values.
03
MappingTurn raw channels into rooms, types, and capabilities.
04
ControlKeep commands and live states in your platform.
01Client Wiren Board02MQTT gateway03Your platform
We are expanding the controller list — new integrations are already planned.
Built to expand
One platform for different systems and assistants
The integration core can be adapted to almost any system when it exposes an API, MQTT, webhooks, or another accessible protocol.
SHDYour platform
One layer for mapping, states, commands, and access rules.
Each new connection is scoped after API reviewThe baseline voice interface for Alice.
A separate voice connection for the customer model you need.
An integration with the Sber ecosystem after API and requirements review.
A company-owned interface inside your environment, when the protocol fits.
Another controller or assistant is not connected automatically: we first review APIs, protocols, and publication requirements.
Built for real installations
Everything required between the controller and Yandex
The OEM layer covers the practical work your integration team performs on every project.
Controller discovery
Connect a project and inspect what it exposes.
Device mapping
Choose a stable customer-facing model.
Rooms and types
Keep voice control understandable.
Capabilities and properties
Expose the right controls for each device.
Account linking
Connect each customer to their project.
Live device states
Reflect current values in the Smart Home layer.
Command routing
Send actions back to the right controller.
Diagnostics
See failures before they become support tickets.
What is different
A company integration, not a generic bridge
The customer sees your skill and domain. Your team controls the project workflow and chooses where the platform runs.
Typical third-party bridgeYour OEM platform
Provider's brandYour brand
External accountYour customer relationship
Provider infrastructureYour infrastructure
Service can disappearYou operate the platform
Limited configurationYour mappings and templates
One external serviceA reusable integration for every project
The plan defines the deployment boundary; your company owns the customer-facing skill.
Who it is for
For smart-home integrators
A practical integration layer for teams delivering Loxone and Wiren Board projects.
Loxone integrators
Add a branded Yandex Smart Home layer to every Miniserver project.
Wiren Board integrators
Turn MQTT-based installations into a consistent customer experience.
Automation companies
Make voice integration a repeatable commissioning step.
Hardware manufacturers
Offer a complete service layer around the hardware you deliver.
Implementation
From first setup to production
We agree the operating model, prepare the integration, and bring the first project online.
Scope
Review infrastructure, brand, controller workflow, and Yandex requirements.
OEM build
Shape the integration layer around the selected company operating model.
Branding
Prepare the customer-facing skill, naming, and onboarding experience.
Infrastructure
Deploy the platform and document the environment for your team.
Yandex setup
Configure account linking, queries, actions, and state notifications.
First project
Commission one real installation and hand over the repeatable workflow.
Adding the next project
Repeat the same setup on the next project
After the initial integration, engineers use the same sequence to connect a controller, choose devices, and test the customer experience.
01New smart-home project
02Add controller
03Discover and select devices
04Customer links your skill
What the integrator gets
A working layer for your projects
You sell the customer a branded skill, while your team gets a repeatable way to connect controllers, map devices, and support live projects.
01Customer layerYour brand, domain, and company skill remain the customer’s point of contact.
02Engineering layerProjects, devices, mappings, states, and diagnostics follow one operating process.
03Operating modelSHD, a separate deployment, API integration, or source delivery — choose the boundary upfront.
The delivery scope and responsibility boundary are agreed before the first project launches.
Questions before implementation
What companies usually ask first
Short answers about ownership, data, controllers, and the operating model.
Is this a separate Alice skill for every customer?
No. Your company operates one Yandex Smart Home skill. Each customer links that skill to a separate project.
Where is customer data stored?
Workspace uses SHD infrastructure. Dedicated uses the agreed deployment environment. With Source delivery, your team operates the environment.
Can we use your admin instead of deploying the platform?
Yes. The Workspace plan runs in SHD infrastructure; your customers still use your skill and your domain. Dedicated plans run outside the shared workspace.
How do customer projects scale?
The number of projects and the operating model are scoped to your team. Choose Workspace, Dedicated, or source delivery for self-managed deployment.
Which controllers are supported?
The current platform supports Loxone and Wiren Board.
Can another controller be added?
Yes. Loxone and Wiren Board are included. A new controller family is a separate integration scope after API and device-model review.
Can our developers change the platform?
Yes, with Source delivery. The standard source package uses a non-exclusive company license. Exclusive rights and redistribution rights are negotiated separately.
What happens after launch?
Workspace includes platform operation, standard updates, basic monitoring, and correction of reproducible platform defects in the monthly fee. Dedicated maintenance, updates, infrastructure operation, and SLA require a separate support agreement. With Source delivery, your team operates the deployment; further development and support are separate.
Who owns the Yandex skill?
The production skill should be registered and operated under the customer company's account.
Can we resell the platform to other integrators?
Not under the standard company license. It is intended for servicing your own end customers. OEM resale or redistribution rights require a separate agreement.
Choose your operating model
Let’s decide how your team will use the integration
Tell us whether you need the SHD workspace, a dedicated deployment, or source delivery. We will confirm the scope and price.
The first call checks the controllers, domain, Yandex account, and deployment model.