Skip to content

🌌 OpenAstro: Pitch Deck for New Recruits

Build a distributed amateur telescope network that does what no single telescope—professional or otherwise—can do.

The Problem We Solve

Three Unsolved Mysteries in Astronomy

1. Where do Fast Radio Bursts come from? - Millisecond blasts of radio energy from deep space - We've never caught an optical counterpart (visible light) - One repeater, 50 synchronized telescopes watching = capture the flash - Existing networks (LCOGT) tried it. They didn't find it—but they proved the flash is fainter than Theory X predicted. That's a publication.

2. What are asteroids really made of? - When an asteroid crosses a star, its shadow traces across Earth at 10–30 km/s - Different sites see different "chords" across the shadow - 5 chords = full 2D shape reconstruction with kilometer precision - A single telescope sees one chord. A network sees the shape. - Real example: The Unistellar Network (citizen scientists with eVscopes) discovered rings around Haumea and Quaoar. NASA's Lucy mission relied on this data.

3. Do hidden planets orbit distant exoplanets? - Transit Timing Variations (TTVs): tiny deviations from a perfect orbit caused by a hidden planet's gravity - Detecting TTVs requires monitoring the same target every clear night for 5–20 years - A single site can only observe 4–6 hours per night (Earth's rotation) - A distributed network observes the same target 24 hours a day - Hidden planets become measurable. The network becomes the instrument.

The Architectural Advantage

No single telescope—not Hubble, not JWST, not Rubin—can replicate geographic distribution.

  • Hubble: Too narrow field of view for occultations
  • JWST: Too expensive and rare to queue-schedule for time-critical events
  • Rubin: Optimized for wide-field surveys, not precision photometry of specific targets
  • Amateur networks: Always on, globally distributed, free to point anywhere

OpenAstro doesn't compete with professional telescopes. It does what they structurally cannot.

What We're Building

Tier 1 Science (Year 1)

Science Case Why It Matters Team Role
Stellar Occultations Asteroid/TNO shapes with km precision. Ring discoveries. Geographic scheduler, light curve pipeline
Exoplanet TTVs Hidden planet inference via timing analysis. Ground-truth for new discoveries. Time-series analysis, n-body solver
Fast Radio Burst Counterparts Constrain FRB physics through upper limits. Even non-detections are papers. Real-time alert system, stacking pipeline

Tier 2 Science (Year 2)

  • Asteroid astrometry for NEO orbit refinement
  • Variable star monitoring (recurrent novae, cataclysmic variables)
  • Microlensing events — detect planets around distant stars via gravity bending light

Why This Works

  1. Irreplaceable science: No single telescope can do this. Professional surveys can't respond quickly enough.
  2. Observable targets: TESS finds exoplanet candidates. ZTF alerts on transients. ESO occultation prediction services exist. We don't need to discover targets—we process them better.
  3. Clear success metrics: Every light curve has a quality score. Every campaign has a completion state. Every paper has a publication.

The Team We Need

Phase 1 (0–3 months): Core Tech Stack

Role Responsibility Skills Required
Backend Engineer FastAPI server, SQLite → PostgreSQL, REST API for telescope clients. Scheduler core logic. Python, databases, async/concurrency
ML/Optimization Engineer Greedy handover algorithm: given 50 sites and 100 targets, assign sites to maximize science value. Algorithm design, Python, optimization (or eagerness to learn)
Data Pipeline Engineer FITS calibration, WCS alignment, flux normalization across heterogeneous instruments. Astropy deep expertise. Python, image processing, photometry
Frontend/Infra Engineer Client software (Raspberry Pi compatibility). Deployment, monitoring, fail-safe systems. Python, devops, or JS/web depending on client approach
Community Manager Discord, outreach to amateur astronomy forums (Cloudy Nights, AAVSO, IOTA), recruitment, retention. Communication, astronomy interest (not expertise required)

Phase 2 (3–12 months): Volunteer Network Expansion

  • Science Lead: Professional astronomer or experienced amateur to validate science quality
  • Telescope Operators: Early volunteer sites running the client software
  • Data Analysis: Amateur astronomers who love reducing light curves

Phase 3 (Year 2+): Owned Hardware

  • Hardware Engineer: Assemble low-cost robotic nodes (Sony Starvis cameras, mounts, automation)
  • DevOps: Scale from 10 sites to 100+ sites. Cloud scheduling. Data warehousing.

The Path to Impact (Real Timeline)

Stage 1: Prove the Pipeline (3–6 months, zero volunteers)

  • Pull AAVSO archival data, ETD exoplanet database, MPC asteroid astrometry
  • Run calibration pipeline on existing observations
  • Produce one publishable result (period refinement, TTV analysis, etc.)
  • Why this works: Validates the entire tech stack with zero recruiting risk. First paper goes to arXiv with your names on it.

Stage 2: Live Volunteer Network (6–18 months, 20–50 observers)

  • 5 volunteer sites running the client
  • First multi-chord occultation campaign (publishable result)
  • Continuous TTV monitoring of high-interest exoplanet system
  • Monthly newsletter with results
  • Why this works: Real data from real telescopes. Real papers with volunteer co-authorship.

Stage 3: OpenAstro-Owned Hardware (18+ months, 50+ total sites)

  • 5–10 network-owned robotic nodes at strategic longitudes
  • Autonomous observation and data upload
  • 24/7 coverage for time-critical transients
  • Why this works: Fills gaps in volunteer coverage. Always-on backbone.

Why Join

For Engineers

  • Real impact: Code you write processes data from actual telescopes in real-time.
  • Publication: Every software contribution gets co-authorship on papers.
  • Technical depth: Distributed systems, optimization, image processing, real-time scheduling—all in one project.
  • Building in public: Open-source from day one. Your work is visible.

For Astronomers (Professional or Amateur)

  • Irreplaceable science: This project does something no single telescope can do.
  • Co-authorship: Observer + analyst = paper. Every meaningful contribution is named.
  • Mentorship: Professional astronomers mentor amateur observers. You learn the cutting edge.
  • Discoveries: First multi-chord occultation network. First distributed TTV inference pipeline.

For Community Builders

  • Growing a movement: 20 observers today → 200 next year → international network.
  • Structure: Community playbook already written (Discord, mentorship, incentives, retention strategy).
  • Visibility: Recognized in papers, newsletters, public dashboards.

The Ask

We're seeking 4–5 core team members to ship Stage 1 in the next 3–6 months.

Minimum Commitment

  • 10–15 hours/week for 3–6 months to reach the first paper
  • Part-time OK. This is volunteer-friendly by design.

What You Get

  • Co-authorship on the first paper (your name in a real publication)
  • Open-source portfolio: GitHub profile with real scientific code
  • Network: Connections to amateur astronomers, citizen scientists, and professional astronomers worldwide
  • Ownership: Your code, your design decisions, your impact

What This Is NOT

  • Not a startup with growth pressure or fundraising
  • Not a pivot to commercial space or hardware sales
  • Not a "nice-to-have" side project (it's a real science pipeline)
  • Not "download our code and contribute" (you're a co-founder, not a contributor)

Why Now

  1. TESS is flooding us with exoplanet candidates — need to confirm and characterize them
  2. Distributed telescope hardware is cheap — a capable amateur scope is $3k–$6k
  3. We've proven the science is irreplaceable — Unistellar Network, IOTA occultations, ExoClock, AAVSO all growing
  4. The tech stack is ready — Python, Astropy, FastAPI, SQLite → PostgreSQL are all mature
  5. There's no competitor doing this yet — the space is open

The Secret

The hard part isn't the astronomy. It's the engineering.

Professional astronomers can write a TTV analysis paper. But building a system that ingests data from 50 heterogeneous telescopes, corrects for atmospheric seeing and instrument differences, and produces light curves that feed into a publication pipeline—that's an engineering problem.

That's what you're solving.

Success Looks Like (6 months from now)

  • [ ] Pipeline runs on 100 AAVSO observations from 10+ different instruments
  • [ ] One publishable result posted to arXiv
  • [ ] GitHub repo with 500+ stars (technical credibility)
  • [ ] First 5 volunteer sites recruiting (beta testing)
  • [ ] First small group of co-authors identified
  • [ ] Newsletter reaching 200 interested observers

Contact & Next Steps

This is a real project with real science and real impact. Not a hypothetical.

If you're interested in: - Building distributed systems that do science - Publishing papers (even if you're not a PhD) - Leading a scientific community from the ground up

Let's talk.

OpenAstro: What one telescope can't do, 50 can.