Testbed Observatory
Validate real-world automation, weather response, optical trains, calibration, storage and staff procedure before public scaling.
- SQA130 testbed rig
- SCA310 detail testbed rig
- Atlas / NINA / data-flow validation
Crux Tools / Observatory Instruments
Crux Karoo Observatory is being developed as a phased southern-sky data and guest-experience platform. Each telescope system has a clear role: testbed validation, public data production, rental imaging, deep detail work, education, media, or future specialist expansion.
Phase breakdown
The telescope plan grows with the site. The early phases prove the operational spine and data engine; later phases turn the proven system into public access, media and premium guest astronomy.
Validate real-world automation, weather response, optical trains, calibration, storage and staff procedure before public scaling.
Turn Crux into a working data-production observatory with a repeatable public southern-sky dataset engine.
Expand into rental rigs, education, media, event capture, guided imaging and broader telescope access.
Use the proven observatory system as the heart of the retreat, Sky Theatre, room workstations and premium astronomy experiences.
03 / Rig Lanes
Rig lanes show planned suitability and phase intent. They do not expose live operations, public booking status, confirmed queue allocation, or telescope availability.
Planned lane does not mean confirmed telescope time. Availability, weather and capture acceptance remain review-gated.
Public dataset lane
Widefield, nebula, mosaic and public dataset production.
Widefield lane
Large nebulae, target discovery, widefield references and guided public routes.
Detail lane
Galaxies, compact nebulae, planetary nebulae and higher-detail crops.
Development lane
Operations testing, calibration, Atlas/NINA validation and early project readiness.
Guest support lane
Education, beginner imaging, guided sessions and guest-facing interpretation.
Destination layer
Premium data handovers, retreat programming, theatre content and guest workstation routing.
Please note that planned capability, commissioned capability and confirmed availability are three different states. This tool recommends a planning path, not a telescope reservation.
Operational assessment
Crux is not buying isolated telescopes. It is building a disciplined capture, processing and delivery system around each rig family. Open a phase to inspect the validation goal without turning the page into a long wall of rig notes.
Internal proving ground for optics, weather response, Atlas/NINA handoff, calibration, storage and staff procedure.
One SQA130-class rig and one SCA310-class rig create two demanding validation lanes: premium refractor workflow and deep-detail obstructed-optic workflow.
Tests automated capture, focusing, rotator behaviour, flats, calibration, data movement and dataset packaging.
Tests guiding precision, tighter sampling, obstruction-aware timing, compact targets and higher operational discipline.
First data-production layer: prove capture, verification, processing, storage, sale and delivery of southern-sky datasets.
The first major Crux data system should prove that the site can operate repeatably and package premium data products without needing the later destination layer first.
Seven parallel SQA130 collectors increase signal depth while retaining a single-rig field-of-view logic.
Supports individual target programmes, medium-wide imaging, calibrated releases and future large-frame validation.
Continues detail testing and early high-resolution target programmes once the rig is validated.
Confirms capture manifests, frame scoring, calibration, archive status, delivery packs and customer communication.
Expands the working observatory into guided access, rental paths, media, education and broader public-facing use.
Phase 2 should not invent a new observatory promise. It should turn the proven technical system into a controlled public platform.
Flexible public-facing platform for broad southern targets, guided sessions and colour/mono product routes.
Balanced premium imaging with IMX571 mono and possible large-frame IMX461 products after validation.
Detail specialist for small galaxies, planetary nebulae and compact structures that benefit from tighter sampling.
Accessible robotic imaging for visitors, school groups, beginner field nights and public demonstrations.
Destination layer built around already-proven observatory systems, Sky Theatre interpretation and premium handovers.
By Phase 3, the telescope systems should already be proven. The guest experience then presents a working observatory, not a promise.
Seestar, SQA106 and selected SQA130 workflows support beginner-to-intermediate guided astronomy experiences.
Atlas Array, Grand Frame and Galaxy 310 systems support calibrated datasets, processed products and print-scale results.
Night reports, all-sky context, target stories and Atlas summaries become part of the guest-facing observatory narrative.
The proven rig family supports private astrophotography workshops, corporate retreats and educational residencies.
Graphic system
The website should denote each rig family with a simple SVG graphic. These are not decorative icons; they are small instrument diagrams that help visitors understand role, scale and behaviour at a glance.
The glyphs use a dedicated telescope language: aperture rings, sensor frames, optical axes, array nodes and obstruction markers. This keeps them visually separate from calendar, moon, weather and status glyphs elsewhere in the toolchain.
Use copper for identity and optical emphasis, not for general status.
Show array rigs as multiple synchronized collectors, while keeping FOV language single-instrument.
Show the SCA310 with a central obstruction marker so exposure planning remains honest.
Use sensor rectangles to indicate IMX585, IMX571 and IMX461 configuration families.
Keep all glyphs line-based, quiet, scalable and suitable for future engraving or dashboard use.
Never use the same glyph family for observatory status, calendar scoring or weather signals.
Rig family assessment
These cards describe the intended role of each rig family. Actual public availability depends on commissioning, field testing and final data-quality validation.
Rig / SQA106
Flexible premium widefield platform for large southern fields, visitor imaging paths and future Dragonfly-style depth work.
Rig / SQA130
Balanced premium imaging workhorse for medium-wide targets, production datasets and the core Atlas Array architecture.
Rig / SCA310
Longer-focal-length detail platform for galaxies, planetary nebulae and compact structures, with obstruction-aware exposure planning.
Array / Atlas
Seven matched SQA130-class collectors working as the first flagship public data engine for repeatable southern-sky releases.
Array / Dragonfly
Future specialist widefield system for deep field work, large southern mosaics and parallel capture programmes.
Guest / Seestar
Accessible robotic imaging path for visitors, school groups, beginner sessions and simple public demonstrations.
Summary matrix
The matrix keeps the public story honest: some systems are testbed, some are production, some are future expansion candidates, and only commissioned systems become bookable.
| Rig family | Phase introduced | Main role | Best use | Website status |
|---|---|---|---|---|
| SQA130 Testbed | Phase 0 | Workflow validation | Medium-wide nebulae, automation and calibration testing | Planned / internal |
| SCA310 Testbed | Phase 0 | Detail validation | Galaxies, compact nebulae, longer-focal-length workflow | Planned / internal |
| Crux Atlas Array | Phase 1 | Main data engine | Deep southern datasets, public releases, data products | Planned flagship |
| SQA106 Widefield | Phase 2 | Rental widefield | Large nebulae, star fields, guided widefield capture | Future public rig |
| SQA130 Precision | Phase 1–2 | Balanced premium imaging | Medium-wide targets, galaxies, clusters, public data | Planned production |
| SCA310 Galaxy / Core | Phase 0–2 | High-resolution detail | Galaxies, planetary nebulae, compact targets | Commissioning-dependent |
| Guest Smartscope Array | Phase 2–3 | Outreach and education | Bright targets, school sessions, beginner imaging | Future public rig |
| SQA106 Dragonfly Array | Future Phase 2+ | Specialist widefield depth | Large southern mosaics and faint wide structures | Expansion candidate |
Choosing a rig
The telescope choice should follow the target, field size, desired result and dataset tier. This roadmap gives context; the Rig Chooser and planning tools handle practical fit.
Choose SQA106, SQA130, Atlas Array or Dragonfly when the target needs context, star field structure or a broad nebula frame.
Choose SCA310, SQA106 + IMX585 or SQA130 + IMX571 for galaxies, compact nebulae or tighter framing.
Choose Atlas Array, Dragonfly or Guest Smartscope Array when the priority is parallel collection or a public array experience.
Choose Seestar, guided SQA106 colour, or field kits when the experience matters more than technical configuration.
Commissioning transparency
Planned hardware should not be presented as operational until it has passed commissioning. This protects the guest experience, the data product and the Crux brand.
Optical train, spacing, tilt, field and backfocus validation.
Autofocus, guiding, rotator, meridian and safety-interruption testing.
Flats, darks, bias/dark-flats, calibration frames and repeatable dataset structure.
Atlas / NINA / Rig Agent integration and job-state reporting.
Data transfer, archive, Parow handoff and delivery package verification.
Staff SOP sign-off, customer wording and website status update.
Crux does not sell a telescope night as a promise of hardware. It sells a disciplined southern-sky data workflow.