01 / Explore
Use the specialist tools.
Check season, rig fit, field of view, mosaic scope, dataset effort and target suitability. Each tool creates planning context, not a final commitment.
Crux Tools / Capture Requests
How Crux capture requests work.
Crux planning tools help visitors describe a target, rig preference, mosaic route and dataset intent. They do not create an automatic quote or booking. Every request is routed through the Capture Package Builder and then reviewed by Crux before any capture path is confirmed.
Single Endpoint Rule
All specialist tools lead into the Capture Package Builder. The builder collects matching planning artifacts, excludes stale or mismatched context, and then hands the final package into the contact form.
02 / Collect
Build one package.
The Capture Package Builder becomes the single final artifact. It collects matching tool context and blocks stale cross-target context from the final brief.
03 / Submit
Send the package brief.
The final request is submitted through the website contact form. This gives Crux a structured starting point for review.
04 / Review
Crux checks feasibility.
Crux reviews target altitude, season, weather window, Moon sensitivity, rig availability, panel count, dataset tier and processing expectation.
05 / Respond
You receive a proposed route.
Crux responds with the recommended capture route, changes needed, possible timing and whether the request is best handled as source data, reference data or showcase output.
06 / Confirm
Only then can capture proceed.
A planning brief is not a quote, booking or observing commitment. Scheduling and delivery are confirmed only after manual review.
What the tools calculate
Planning evidence.
- Target size, season and Southern Hemisphere suitability.
- Rig fit, FOV coverage and preliminary mosaic shape.
- Panel count, panel-centre vectors and coverage footprint.
- Dataset tier estimate, capture hours, nights and storage footprint.
- A structured capture package draft for submission.
What Crux still reviews
Operations reality.
- Actual observing window, target altitude and Moon/weather conditions.
- Rig availability, technical suitability and array scheduling.
- Mosaic feasibility, panel overlap and final composition intent.
- Processing level, delivery format and retention requirements.
- Whether the request should be adjusted before acceptance.
After submission
The submitted package gives Crux enough context to respond intelligently. It does not force the original tool result to be accepted unchanged. Crux may recommend a different rig, a smaller mosaic, a different delivery tier, or a better seasonal window.