Skip to content

Onboarding and application

This page is for telescope owners — universities, research groups, and educational institutions — who want to bring an observatory onto the Skynet Global Observatory.

It covers two things:

  1. Why partner with Skynet — what you gain, and what you keep control of.
  2. What the onboarding flow looks like end-to-end — the concrete steps from “we’re interested” to “our telescope is taking observations through Skynet.”

If you’re a researcher looking to use telescopes on Skynet rather than contribute one, see the Observers section instead.


Skynet is an end-to-end, API-first observing platform that connects telescopes, researchers, educators, and students into one global ecosystem. Joining Skynet lets your observatory:

  • Reach a global user base without giving up local control. Skynet’s scheduling layer matches incoming observation requests to telescopes that can fulfill them, and your access-control policies decide who’s eligible.
  • Stay productive year-round. Idle time on your telescope can be made available to partner organizations, exchange programs, or the Skynet community — at your discretion — instead of going unused.
  • Run educational programming through a turnkey platform. Classroom integrations, lab-style observing assignments, and student accounts come out of the box. Academic observatories get a real audience for their instruments.
  • Participate in coordinated science. Skynet powers kilonova searches, supernova monitoring, asteroid tracking, exoplanet surveys, and alert-driven follow-up campaigns. Partner observatories earn publication credit on resulting science.
  • Integrate heterogeneous hardware. SkyNode supports a wide range of optical and radio instruments via plugin drivers; common combinations (ASCOM mounts, MaxIm cameras, off-the-shelf weather sensors) work without custom code. See the device wiring pages for current driver coverage.
  • Keep authority over your telescope. You decide who can submit observations to your queues, how time is prioritized, when the telescope takes manual override, and what data goes public. Skynet is the coordination layer; it is not a replacement for your control system.

Under the hood, a shared data model is what lets a federation of differently-designed telescopes behave as one coordinated instrument.


Joining Skynet does not transfer ownership or operational authority. Every participating observatory retains:

  • Hardware ownership — the telescope, mount, instruments, and site are yours.
  • Access policy — which users and organizations can submit observations, and how their requests are prioritized.
  • Queue configuration — the ordered list of observing queues on each telescope, their prioritization model (only fixed is live today), and who can hold time on each.
  • Operational windows — operational constraints and shutdown interlocks that gate when the telescope is eligible to take observations. SkyNode evaluates weather-sensor and mount–Sun separation constraints today; see Observing policy and shutdown interlocks.
  • Manual control — at any time, the operator can switch SkyNode to MANUAL control at the node, suspending automated scheduling and giving the local operator full control; a web user can likewise take the telescope’s manual-control lease from the telescope console.

Skynet’s job is to coordinate; your observatory’s job is to operate.


The realistic path from interest to first automated observation looks like this. Steps marked (staff) are completed by Skynet operators on your behalf; steps marked (you) are owner-driven.

Contact Skynet (contact@skynetgo.org) to start the conversation. We discuss your hardware, science goals, network expectations, and how your observatory fits into the broader federation. The written telescope application comes after your organization exists (step 2).

2. Create user and organization records, and apply — (you + staff)

Section titled “2. Create user and organization records, and apply — (you + staff)”

Sign up at the Skynet web app. Organizations are created by Skynet staff: staff create your university’s or institute’s organization record and invite you with the owner role; once you accept, you invite other operators and assign their roles.

  • The organization owns the observatory record (created in step 3).
  • Roles within the organization control who can edit observatory settings, manage telescope queues, grant access, and so on; see Entities for the built-in roles.

Then submit a telescope application for each telescope: Organization → Settings → Telescope Application → Start application. It needs the owner or device manager role. The form asks about the telescope (optical imaging, radio, or something else), its site and hardware; rough answers are fine, and they decide sequencing, not acceptance. The same settings page lists your submitted applications with their status as staff move them along: Submitted, Under review, Accepted, Scheduled, Provisioning, Onboarded, or Deferred (parked for a later cohort).

3. Provision the site and observatory records — (staff)

Section titled “3. Provision the site and observatory records — (staff)”

Sites and observatories are created by Skynet staff today (the API refuses creation from anyone else; owners can only edit them afterwards via PATCH). Skynet staff create:

  • A Site record for the physical location (lat/lon, elevation, country, optional IAU code).
  • An Observatory record on that site, owned by your organization.

Once the records exist, you set the observatory’s photo on its Overview page in the web app, and configure its weather sensors and operational constraints from SkyNode. The other fields (name, description, public visibility) are edited through PATCH /v1/observatories/{uid} or by Skynet staff; the web app has no observatory settings page.

For each telescope at the observatory, Skynet staff create the Telescope record (creating one through the API requires a staff permission). A Telescope ties together a mount, optional enclosure, a set of devices (cameras, filter wheels, focusers, OTAs, …), and an ordered list of observing queues. Once it exists, you edit it on the telescope’s Settings tab.

The full Telescope schema is in the API reference; the owner-facing view is at Telescope.

SkyNode is the agent that runs at your site and bridges your hardware to Skynet. Install it on a machine that can talk to your devices, then OAuth-pair the install with the hub. Pairing creates a SkyNodeInstallation record bound to your telescope (or to the observatory, for observatory-level deployments).

See SkyNode → Overview for the install path and configuration reference.

In the SkyNode local GUI’s configuration page, declare each physical device (mount, camera, filter wheel, focuser, OTA, enclosure, weather sensor, …). For each, choose the driver, set connection parameters, and verify the device comes online. Skynet currently ships drivers in four families:

  • ASCOM — mounts, cameras, filter wheels, focusers, enclosures, and OTA covers (cover calibrator).
  • MaxIm DL — cameras and filter wheels.
  • Native — GBTwenty mount; Astrohaven clamshell enclosures and New Mexico Skies roll-off roof status; AutoSlew (Astro Optik) mirror covers and fans; AAG CloudWatcher, Aurora Eurotech, Boltwood I/II, Cumulus, Davis WeatherLink, Green Bank and SkyCanary weather sensors; Amcrest / Dahua CGI and ONVIF IP cameras.
  • Simulator — every device type except IP cameras has a simulator driver so you can rehearse a configuration before hardware is on site.

The full list is in SkyNode → Drivers; per-device-type wiring guides are under SkyNode → wiring. Instrument rotators, receivers and radio backends have only simulator drivers at present.

Decide who can use the telescope.

  • Observing queues — every telescope starts with Maintenance, TOO, Calibration and General queues. You order them, choose each one’s prioritization and decide who holds time on each; see Configure queues.
  • Telescope access grants — give a specific user or organization a share of time on the telescope; queue access grants then admit that grant to particular queues. They do not give authority over the telescope’s settings, which comes from your organization’s roles.
  • Observing accounts — entities can aggregate one or more queues across telescopes into a single observing account, which is what observers submit requests against.

See Telescope access for the model.

With the telescope active and queues configured, submit a test observation against your own observing account. Verify that:

  • SkyNode picks up the task from the hub.
  • The mount slews, the enclosure opens (or the operator opens it manually), and the camera/receiver acquires.
  • Results are uploaded and visible in the observation detail page.

Flip the telescope’s isAvailable flag to true (and isPublic if you want it discoverable to all Skynet users). Open up queue access to the intended audience. From here forward, the telescope is operating as a member of the network.


If something here is wrong or out of date, please flag it — onboarding flow is the part of the docs that decays fastest as the platform evolves.