Build the next connector. Or the next product.

A contract generated from the running code, SDKs generated from the contract, and a sandbox that behaves like a real home because it is one.

Create a developer account Developer sign in Read the docs

// npm i alyt-sdk
import { createAlyt } from "alyt-sdk";

const alyt = createAlyt({ appId, appSecret });

const things = await alyt.thingsList({ room: "kitchen" });
await alyt.endpointsCommand(things[0].id, {
  capability: "light", key: "power", value: true
});

# pip install alyt-sdk
from alyt_sdk import create_alyt

alyt = create_alyt(app_id=APP_ID, app_secret=APP_SECRET)

things = alyt.things_list(room="kitchen")
alyt.endpoints_command(things[0].id,
    capability="light", key="power", value=True)

curl https://developers.alyt.com/v1/things?room=kitchen \
  -H "Authorization: Bearer $ALYT_TOKEN"

curl -X POST https://developers.alyt.com/v1/endpoints/$ID/command \
  -H "Authorization: Bearer $ALYT_TOKEN" \
  -d '{"capability":"light","key":"power","value":true}'

What you get

A published contract
243 operations, every one with a summary, a description and a typed response, generated at request time from the services' own route tables. A CI gate fails when it drifts.
Two SDKs
TypeScript with no runtime dependencies and Python, both generated from the contract and versioned by its diff. One entry point: create a client with an app id and a secret.
A sandbox that is a real tenant
Its own property, seeded rooms and five virtual devices, with the same isolation, broker permissions and query narrowing as production.
Virtual devices on the real broker
Hub, speaker, light, sensor and thermostat profiles. Scenarios: offline, low battery, sensor error, burst, flapping, slow. The platform cannot tell them from hardware.
Signed webhooks and a stream
Deliveries signed with a timestamp and an HMAC, retries doubling to an hour, and a Server-Sent Events stream that resumes from the last id.
Submission and review
Draft, review, approval, publication. Automated checks, a probe against isolated credentials, then a human. Your connector reaches every home on release.

Events you can subscribe to

device.online
device.offline
device.telemetry
command.result
notification.raised
thing.state
submission.state
guest.invited
guest.checked_in
guest.checked_out

Scopes

things:readread things and their state
things:controlsend commands
integrations:readread the catalogue
events:readthe stream and webhooks
webhooks:writemanage endpoints
simulator:writevirtual devices

Test with Simone on ALYT GPUs

Request access to ALYT’s GPU-powered development environment to test your apps and connectors with Simone. Open AI settings and usage in your app dashboard to apply. Access requires approval and comes with a usage allowance; it is for development, not production. You can also bring your own provider key.

Create a developer account

Build the next connector. Or the next product.

What you get

A published contract

Two SDKs

A sandbox that is a real tenant

Virtual devices on the real broker

Signed webhooks and a stream

Submission and review

Events you can subscribe to

Scopes

Test with Simone on ALYT GPUs

Give your things a home that thinks.