Participate in the developer community

Every community connector on ALYT has a public page that shows what it does, who published it, how it connects, and what happens when it is disconnected. The catalogue is read live, so new publications appear without waiting for a static build. A developer can search by connector name, publisher, or device category, open the connector details, read the prose, and follow a link to the connector JSON.

What you can see

The community catalogue lists published connectors with a short set of fields that are useful for evaluation:

• connector name and version
• publisher name and submitting developer name
• a verification badge for the author identity
• what the connector brings
• how it connects
• whether it uses ALYT inference, a cloud AI provider, a local model, or no AI
• the published date
• the consequence when it is disconnected
• links to the publisher website, support, and privacy policy when provided

The page also shows the connector prose in readable form, so a person can review the same description that is published to the catalogue.

How publication works

Community connectors are not listed until they have gone through the published flow. The visible experience reflects that flow: a developer submits a connector, the page is generated from its descriptor, machine checks run, a probe verifies the claims that can be checked, and a person approves publication.

That means the catalogue is useful both for discovery and for trust. A verified badge means the publisher identity is verified. It does not mean the connector is high quality or endorsed.

Searching and opening a connector

The catalogue includes a search field. You can search by connector name, developer, or device category. When a connector matches, its card appears in the grid. Opening the details reveals the published date, connection method, disconnected behavior, the rendered prose, and a link to the JSON representation.

If no connectors are published yet, the page tells you that and offers a path to build the first connector.

What the page is for

For most developers, the connector is the product. They are not starting from a blank API surface; they are asking whether ALYT can talk to the devices already present in a customer’s houses, and what stops working if the connector is unavailable.

That makes the community page a practical reference, not a marketing list. It helps you answer:

• what a connector adds to a house
• whether it is local, cloud, or cloud-then-local
• how a person connects it and what that requires
• what discovery it supports
• what stops working when it is disconnected

Local and cloud behavior

If a connector is local, it can continue working during a cloud outage. If it depends on a cloud provider, its cloud path and network must be available. The catalogue reflects that by showing the connector’s declared connectivity and its disconnected consequence.

This distinction matters for evaluation and support. A developer should check the connector page before promising behavior in an outage.

Community content and the API

The community page is backed by the same structured connector data that powers the catalogue. That allows a connector to be shown both as a human-readable page and as JSON for an agent or integration workflow.

For developers building against the platform, this means the public catalogue is also a source of structured connector information. It is not a separate editorial system.

Permissions and visibility

The community catalogue is for published connectors. It is not the place to inspect private draft work. Access rules follow the normal developer portal boundaries: household permissions are narrower than staff, DEV credentials act in the developer sandbox, and LIVE credentials only apply to the developer’s own installed connector.

If you are evaluating a connector for a specific deployment, use the published page as the reference for what is available publicly, then test it in the appropriate environment.

What to expect from a connector page

A useful connector page answers the operational questions quickly:

• what the connector supports
• who published it
• how it connects
• what it uses for AI, if anything
• what changes when it is disconnected
• where to find support and policy details

That is the standard for the community catalogue, and it is the standard developers should use when deciding whether a connector fits a project.