Test an application in an approved home

Developers can test a private connector in an approved home after they confirm the home owner by email, choose one home they own, and enable one connector version for that home. This is separate from review and release: approval alone does not grant customer access, and a private test does not create a household login, a home merge, or a general DEV-key claim on a real home.

Before you start

Use a version that already works in your own HTTPS runtime and requires its ALYT runtime token. For private tests, direct connect forms are supported. OAuth and external app linking are available only after publication. The home owner must have an unconditional current OWNER membership at the time you enable the test, and normal household permissions still apply once the connector is installed.

Start in the sandbox with virtual devices if you want to verify basic behavior first. DEV credentials stay in the developer sandbox. A linked home only narrows access for that confirmed home; it does not open other homes or other devices.

Confirm the home owner

Open /dashboard/homes and send a confirmation request to the home-owner email address. You can use the same address as your developer email or a different address that owns the ALYT home. Confirmation is always required.

The owner receives a 30-minute single-use token. They open the link, see which developer is requesting access, choose one currently owned home, and confirm it with a POST. Tokens travel in URL fragments and POST bodies, and the page removes the fragment before further navigation. Only token hashes are stored.

Requests are limited to six per hour per developer and recipient mailbox. An independent removal token is also sent to the owner. If removal delivery fails, the grant is revoked.

Enable a private test

After confirmation, refresh the home list and the version list. Choose one confirmed home and one connector version, then enable the private test. A private Development tile appears only for that owner in that home. The owner installs it in the ordinary ALYT app, and the home owner’s normal permissions govern which connected devices are available.

Other households and the public catalogue cannot see the private version. The developer supplies the hosting. Missing test records fail closed. Unlinking the home, disabling the test, loss of ownership, or account suspension blocks later private runtime calls and new installations.

What the owner sees

The owner signs in to the ordinary ALYT app, selects the owned home, and opens Connectors. They see the private Development tile only for that home. This is not a public catalogue listing, and it does not change production integrations.

If the owner later removes the testing permission, private tests associated with that link stop. Existing household memberships and production connectors remain unchanged.

Access boundaries

A confirmed test home grants only the access needed for that private connector test. Household members can use its installed devices under normal home permissions, but the linked home does not grant household login or broader account access.

A current confirmed link also does not make the connector public. If the version later becomes public, the testing restriction remains attached through Integration.developerHomeTestId. Existing installations keep their recorded version, including runtime URL and token, so a newer version does not silently redirect an older installation.

What stays out of scope

Private home testing does not cover hosted executable uploads, local WASM connectors, or public customer release. It also does not prove vendor authorization or data handling. Automated checks observe protocol behavior only; staff review claims, permissions, support, and privacy documentation separately.

If you need to remove the permission, use the removal link in the owner email or the revoke page. The revocation stops later private tests, but it does not delete the home or production integrations.