Shared observatory controller

Starling

Starling logo
Remotely control your shared observatory: safely, for everyone.

Starling is designed for shared and professional observatories where multiple users need to operate the same roll-off roof. Two access roles—Sentinel and Clients—keep everyone in sync and the infrastructure protected at all times.

Starling

Starling or DragonFly — which is right for me?

Starling

Focused on the roll-off roof and multi-user coordination. For shared or professional observatories where several people use the same infrastructure.

DragonFly

A versatile controller for many observatory elements in a personal or single-user setup — dome, focuser, sensors, flat panel and more.

See DragonFly → Read the full comparison →
Access model

Two roles, one observatory

Starling's role-based model separates infrastructure control from day-to-day use, so every user gets exactly the access they need, and the Sentinel always stays in charge of safety.

Sentinel—Observatory Manager

Full control over the infrastructure

The Sentinel is the observatory owner or manager. They supervise the system, monitor all conditions and can override any client action when needed.

  • Open and close the roof
  • Control any device connected—alarm, lights, dehumidifier, extras
  • Monitor and manage all client requests
  • Connect the CloudWatcher or other safety devices
  • Override safety conditions for manual operation
  • Monitor sensor inputs: roof position, power fail, emergency
Client—Observatory User

Roof control without conflict

Clients are authorised users of the shared observatory. They interact with the roof as if they were the only ones. Starling handles the coordination invisibly.

  • Request to open or close the roof
  • Monitor roof position in a conflict-free single-user view
  • Use third-party automation software via ASCOM driver
  • Access via web control panel or REST API
  • View relay states and safety status—read only

Access is role-based, not device-based: Sentinel and Clients can connect from desktop, tablet or mobile.

Interface

Two panels, two roles

The Sentinel interface gives full diagnostic and control access. The Client panel is focused, clean and designed to be usable from any device.

Starling Sentinel interface—Home page showing diagnostics: system name, firmware version, IP address and system running normally

Sentinel · Home—Diagnostics panel showing system name, firmware version, IP address and overall health status.

Starling client control panel—User name, Roof control buttons, read-only peripherals and Safety information

Client · Control Panel—Simplified panel with user name, roof open/close/abort controls, read-only peripheral states and live safety information.

Starling client control panel viewed on a mobile phone—User, Roof and Peripherals sections stacked for a small screen

Client · Mobile view—The same control panel, responsive and fully usable on a phone screen.

Starling control panel icon pinned to a phone's home screen, next to the regular apps

Pin to home screen—No app needed: pinning the control panel to your phone's home screen gives it an app-like feel.

Starling Sentinel relays and sensors—six controllable relay toggles plus Open roof and Close roof marked Inaccessible (roof control), and eight sensor input readings

Sentinel · Relays & Sensors—The six general-purpose relays can be toggled directly (a double-click is required, so they are only ever changed intentionally); the two roof-control relays show as Inaccessible and should not be operated by hand. All 8 sensor inputs are read live, including roof position, safety state and emergency.

Starling Sentinel configuration—network settings, open/close timeout, flaps, limit switches and access credentials

Sentinel · Configuration—Network settings, open/close timeout, flap control, limit switch polarity, safety closure rules and access credentials.

Starling Software and Firmware Updates panel—current versions and update check buttons

Software & Firmware Updates—Independent software and firmware version tracking with separate update checks and system reboot. The page itself carries the advice: if possible, avoid updating remotely.

Supported roof systems

Works with the roof you already have

Starling is designed as a near plug-and-play solution for professional and semi-professional observatories. It supports a wide range of motorisation types out of the box.

Caterpillar SSR

Full native integration with Lunatico's own Caterpillar SSR roll-off roof controller: the natural combination for a complete Lunatico observatory system.

Third-party motorisation

Compatible with roofs driven by standard third-party motors, including garage door motors and similar automation hardware already installed in many existing observatories.

Three-phase motors with VFD

Supports larger observatory roofs powered by three-phase motors controlled through a Variable Frequency Drive, covering industrial-scale installations.

Roof flaps via linear actuators

Starling can also control roof flap panels—auxiliary side hatches or hinged sections—as long as they are moved by linear actuators. Two of the free relays can be assigned to flap control.

Hardware

8 relays · 8 sensors · DIN rail ready

A complete I/O system for observatory automation. Five relays are pre-assigned to standard observatory functions; three are free for custom needs.

Starling connection label showing all inputs, outputs and power terminals

The connection label provides an at-a-glance overview of all sensor inputs and relay outputs, making installation straightforward and reducing setup errors in real observatory environments.

Relay outputs—8 total

Open roofPre-assigned
Close roofPre-assigned
Service lightsPre-assigned
AlarmPre-assigned
DehumidifierPre-assigned
Extra 1 / Extra 2 / Extra 3Free  Flap-capable ×2

Sensor inputs—8 total

Roof open switchPosition sensing
Roof closed switchPosition sensing
UnsafeSafety monitor
Power failPower monitoring
EmergencyEmergency stop
Security overrideManual override
Open / CloseExternal command
Master CloseForced closure

Technical specifications

Dimensions145 × 60 × 245 mm
Power supply12V DC (up to 24V), <1A, 5.5/2.1mm jack
ConnectionEthernet (direct)
Relay outputs8 (5 pre-assigned + 3 free)
Sensor inputs8
Noise protectionExtremely protected
MountingDIN rail (optional)
Manual controlPhysical buttons/switches
Switched loadAC mains up to 240V, or DC

Earthing is required. The box of the unit must be connected to ground (earth) via the circular banana-style socket on the case—even if every circuit routed through the Starling is D.C.

Local physical controlPhysical buttons or switches can be wired directly to Starling for manual roof operation—open, close, service light, outputs—without needing any computer. Essential for maintenance and on-site access.

Software & integration

Works with your automation setup

Clients connect with their existing astronomy software through ASCOM, or directly via the web control panel or REST API.

ASCOM driver

Full ASCOM dome driver for Windows. Clients keep using their preferred automation software exactly as they would with a personal observatory: no workflow changes required.

SGProVoyagerN.I.N.A.ACP

Web control panel

Two distinct web interfaces: a comprehensive full-control panel for the Sentinel, and a simplified public control panel for Clients, accessible from any browser on any device.

REST API

A simple API enables integration with existing applications, observatory management systems and custom web dashboards, without going through ASCOM. Commands are sent over HTTP as http://starling/api/v1/<group>/<command>/<params>—the same calls the public control panel itself uses—and are Seletek Line Protocol (SLP) commands, documented in the Sentinel manual.

Mobile-friendly

The Starling control panel is fully responsive. Pinning it to your phone home screen gives it an app-like feel: full roof control from any mobile device, no installation needed.

INDILib—coming soon

INDILib support is planned for a future release, extending Starling's compatibility to the Linux and INDI-based automation ecosystem.

Safety model

Safeguards for a shared roof

Starling is designed so that in a shared environment, no single failure or missed logout leaves the observatory open. By default, an active unsafe, power fail or emergency sensor triggers the closing of the roof; the security override exists to suspend that behaviour deliberately.

Close on Sentinel disconnect

If the Sentinel disconnects and this option is active, Starling closes the roof automatically, protecting the observatory even if the manager loses connectivity.

Close if no active clients

If all clients have disconnected and no one is using the observatory, Starling can close the roof, preventing an empty observatory from staying open overnight.

CloudWatcher integration

The Sentinel monitors weather conditions via the Unsafe sensor input, which connects to the CloudWatcher or any other ASCOM safety monitor.

Master Close input

A dedicated Master Close sensor input—wired to a physical switch or an external system—forces the roof to close regardless of any other state or user request. This is the route to use when you need to override the other users: on the control panel the Sentinel's own open and close buttons count as one more user request, so if conditions are safe and other users still want the roof open, it stays open.

Power fail detection

A dedicated sensor input monitors for power failures, allowing Starling to register and react to supply interruptions at the observatory.

Manual security override

The Sentinel can activate a security override to operate the roof manually, bypassing all software safety interlocks when needed for on-site maintenance.

FAQ

Frequently asked questions

What is a shared observatory controller?

A shared observatory controller is a system designed to allow multiple users to safely operate a single observatory infrastructure, coordinating access to the roof, sensors and safety systems without conflicts.

How does Starling manage multiple users in a shared observatory?

Starling uses a role-based model with a Sentinel (observatory manager) and Clients (observatory users). Clients operate under a common access model, while the Sentinel supervises the system and can take over control when required, ensuring conflict-free operation.

Can Starling be used in professional observatories?

Yes. Starling is designed for professional and semi-professional observatories, offering the robustness, reliability and versatility required for demanding installations and continuous operation.

Which types of observatory roofs can Starling control?

Starling supports a wide range of roof systems, including roofs automated with Lunatico's Caterpillar SSR, third-party motorisation systems such as garage door motors, and roofs driven by three-phase motors controlled via a VFD.

Can Starling be integrated with existing observatory software?

Yes. Starling provides a simple API and ASCOM compatibility, allowing easy integration with existing astronomy software, control systems and custom workflows.

Do Sentinel and Clients need different devices to access Starling?

No. Starling is accessed through a web-based interface available from desktop, tablet and mobile devices. Access permissions depend on the user role, not on the device used.

Is Starling suitable for remotely operated observatories?

Yes. Starling is designed for remote observatory operation, providing safe roof control, system monitoring and integration with third-party software in shared and unattended environments.

Availability

Where to buy

A DragonFly wired to the wall of a roll-off roof observatory, telescope on its pier under the Milky Way and capture software running on the screen
Developers

Your observatory. Your software.

Build your own integrations with Lunaticoastro devices. Every command travels over plain HTTP, USB or UDP—one protocol shared across the whole range, so what you learn on one device works on the next.

Explore SLP

391 commands · 12 devices · try one from your browser

Documentation & downloads

Get started with Starling

Separate manuals for the Sentinel (observatory manager) and the Client (observatory user). The ASCOM driver is available for immediate download.