Service status and contact
A developer can check ALYT’s public service health from the footer and use the contact flow for API and integration questions. The status page shows platform services, portals, integrations and local AI, with recorded history for the last 24, 168 or 336 hours, while the contact flow routes developer inquiries to the team with a 48 hours target for the first response. Use the public results as operational signals, not as authorization for device actions, and remember that the page reflects ALYT infrastructure rather than an independent global monitor.
Checking status
Section titled “Checking status”Open System status from the footer before or after signing in. The public page groups platform services, portals, integrations and local AI, and you can search for a component, then choose a 24, seven or fourteen day window. For the public JSON report, the supported hour windows are 24, 168 and 336.
If you need the recorded values for a component, open its hourly report. You can also download the selected window as CSV. All times are UTC.
How to read the charts
Section titled “How to read the charts”Read both availability and Coverage. Availability is the share of successful recorded samples. Coverage is how many expected samples were actually recorded. A high availability percentage with little coverage does not prove uninterrupted service.
New components and gaps begin with no data. The current observations expire after 90 seconds, so a fresh view matters more than a stale one. Partial bars mark recorded checks versus unobserved time.
What the checks mean
Section titled “What the checks mean”Integration checks describe ALYT runtime health. They do not prove that every customer device works, and they do not prove that a third-party provider has no incident.
Local AI checks name their own scope and do not run customer prompts or audio. Automatic incident reports describe observed failures and recovery; they do not invent root causes.
Every public service and catalogue integration remains visible, including Apple TV, Google TV, Apple CarPlay, Android Auto, Matter and HomeKit. If an entry has no central probe, it is shown as unmonitored with unknown availability. It is never hidden and it is never given invented uptime. Only actually monitored services count toward monitored availability.
Contacting ALYT
Section titled “Contacting ALYT”Choose Contact in the footer and select Developers for API or integration inquiries. Include the affected feature and the relevant steps. Leave out credentials, access tokens and private customer data.
When you submit the form, you receive a saved request reference. That does not mean the delivery is confirmed, so keep the reference and check the confirmation. You can reply to ALYT’s acknowledgement to add details.
Access boundaries
Section titled “Access boundaries”Household permissions are narrower than staff permissions. DEV credentials act in the developer sandbox. LIVE credentials work only for their own installed connector.
Use the public status data to monitor service health and to help diagnose issues, but never use a stale status result to authorize a device action.
Founding Installer questions
Section titled “Founding Installer questions”The direct Crowdfunders page offers one $390 USD ALYT Hub AI Founding Installer evaluation kit through direct checkout, with no application or professional approval required. Only one active kit order per buyer email is enforced, and retries reuse the same order. Keep the private payment receipt to check payment or refund status, while historical private application links still work under their original review rules and should remain separate. Purchasing does not create verified partner business status, household access, or commission eligibility. The campaign is an unlaunched preview with Stripe TEST payments, no countdown, and no guaranteed income; the $250,000 target/minimum is proposed, not assured.