PROCUREMENT GUIDE
Ground Station Pricing
A clear, quote-ready breakdown of how ground providers price satellite contacts—so you can compare options and secure capacity with confidence.
Models buyers actually see
Per minute, per pass, reserved capacity, subscriptions, and dedicated leases
What drives cost
Band, throughput, regions, SLA, lead time, and reliability requirements
Make quotes comparable
Send the same mini-SOW to multiple vendors and normalize the terms
GSaaS / Downlink / TT&C / Scheduling / Ops support
This quarter / 6–12 months / Exploring
Single region / 3 regions / Global + polar
S-band TT&C / X-band downlink / Ka-band / Unsure
Passes/day, minutes/month, or GB/day
Standard / Priority / Mission-critical
How ground station pricing works
Ground station pricing is capacity pricing. You’re buying time on antennas (and sometimes service layers on top: scheduling, data delivery, and mission ops). Quotes look simple on the surface (“$/minute” or “$/pass”), but the real cost is shaped by what you need to guarantee: coverage, lead time, throughput, reliability, and operational support.
Antenna time (minutes / passes)
Scheduling guarantees (priority, reservations, conflict handling)
Delivery + ops layers (cloud delivery, security, 24/7 staffing)
HOW TO GET PRICING THAT’S ACTUALLY COMPARABLE
How to request pricing without getting apples vs oranges.
The fastest way to get actionable pricing is to submit one consistent request brief, then compare vendors on the same assumptions: band, coverage, usage, scheduling mode, delivery target, and SLA.
1
Specify what you’re buying
Downlink vs TT&C vs combined GSaaS (include your primary band and mission stage).
2
Quantify usage
Choose one: minutes/month, passes/day, or GB/day—then include a safety buffer.
3
Choose a scheduling model
On-demand for flexibility; reserved/committed for priority and better rates.
4
Define delivery + security
Direct-to-cloud, secure endpoint, encryption, and any compliance constraints.
5
Normalize the quote terms
Compare cancellation rules, included services, and what “SLA” actually covers.
Vendor types that influence pricing.
Pricing varies significantly based on vendor model. Two vendors can quote “per minute,” but include very different service layers and guarantees.
Global shared networks (multi-site)
Best for
Coverage and redundancy with flexible routing
Typical pricing
Per minute/pass; subscriptions for committed usage
What you'll need to provide
Regions, bands, usage, delivery target
Dedicated / single-tenant capacity
Best for
Mission-critical operations and predictable scheduling
Typical pricing
Monthly/annual lease or reserved blocks
What you'll need to provide
Commitment term, station requirements, uptime targets
Cloud-integrated ground services
Best for
Direct-to-cloud delivery and near-real-time processing pipelines
Typical pricing
Antenna time + delivery/storage/egress components
What you'll need to provide
Cloud region preferences, endpoint/IAM details, pipeline needs
Mission ops providers (LEOP, 24/7 console)
Best for
High-stakes phases and operational continuity
Typical pricing
Retainer/subscription + per-contact add-ons
What you'll need to provide
Ops coverage, procedures, escalation SLAs
Scheduling/orchestration platforms (API layer)
Best for
Automation, multi-vendor routing, fewer manual conflicts
Typical pricing
Software license + underlying provider costs
What you'll need to provide
API integration, workflow automation requirements
THE CHECKLIST
Pricing checklist.
Use this to force quotes into the same shape—so procurement and ops can evaluate quickly.
What is priced
• Antenna time billed per minute or per pass (and minimum contact duration)
• Setup fees (if any) and what they cover
• Included services (scheduling, support, data delivery)
Scheduling model
• On-demand vs reserved/committed minutes
• Priority rules and conflict handling
• How far ahead you can schedule and how changes/cancellations are billed
Coverage + bands
• Regions included and polar availability
• Bands supported (S/X/Ka) and constraints
• Elevation mask assumptions and pass duration variability
Throughput + delivery
• Data rate, modulation support, and link budget constraints
• Direct-to-cloud options and delivery format
• Security: encryption, key handling, access control, audit logs
Ops + SLA
• Support tier (business hours vs 24/7)
• LEOP coverage and escalation
• SLA definition (availability, missed contact handling, credits)
Commercial terms
• Commitment term, rollover minutes, and overage rates
• Cancellation windows and penalties
• How changes are handled close to contact time
When each pricing model wins.
Demo missions and early validation
On-demand contacts are ideal when you need flexibility and are still learning your operational cadence.
Operational constellations
Reserved/committed minutes usually win once your contact cadence becomes predictable and you need priority scheduling.
High-stakes phases (LEOP)
Dedicated blocks, premium support tiers, and redundancy often matter more than unit cost.
Direct-to-cloud processing pipelines
Pricing should account for delivery/storage/egress components—not just antenna minutes.
Multi-region redundancy requirements
Network vendors price reliability and reroute capability; compare SLA definitions carefully.
Common pricing models.
On-demand (per-minute / per-pass)
Best for flexibility and early-phase testing
Higher unit cost but no long-term commitment
MOST POPULAR
Reserved / committed minutes
Lower unit rates in exchange for monthly commitment
Improved scheduling priority and guaranteed capacity blocks
Subscription bundles
Predictable spend with included usage tiers
Often paired with support tiers and service-level guarantees
Dedicated leases / single-tenant capacity
Highest cost, highest control and predictability
Appropriate for mission-critical operations and strict SLAs
Pricing depends on your band, throughput, regions, SLA tier, scheduling lead time, and whether you need reserved capacity. Want real numbers? Submit one mini-SOW and get 2–3 comparable quotes.
Ground station pricing FAQs
Is ground station pricing usually per minute or per pass?
Both exist. Some vendors quote per minute of antenna time, others quote per pass/contact. The key is to normalize for minimum contact duration, elevation mask assumptions, and how much of the service layer is included (scheduling, support, delivery).
What’s the difference between on-demand and reserved pricing?
On-demand is pay-as-you-go with maximum flexibility. Reserved/committed pricing lowers unit cost in exchange for a monthly commitment and often comes with improved scheduling priority and capacity guarantees.
What makes quotes hard to compare?
Hidden assumptions: minimum contact duration, included regions, cancellation rules, support tier, and whether data delivery (cloud endpoints) is included or priced separately.
Do I need to pay more for polar coverage?
Often, yes. Polar coverage can require specialized site distribution and higher demand windows. Vendors may price it as premium capacity, especially if your schedule is time-sensitive.
How should we request pricing for a constellation?
Provide your expected passes/day or minutes/month per spacecraft, a target set of regions, and your preferred scheduling mode (on-demand vs reserved). Ask vendors to price both: a flexible plan and a committed plan.
How do SLAs affect price?
Stronger guarantees typically raise price. An SLA can include response times, reroute commitments, redundancy, missed-contact handling, and credits—make vendors state exactly what they guarantee.
Should I buy software separately for scheduling?
Sometimes. If you’re operating across multiple providers or need automation, an orchestration layer can reduce operational overhead and increase effective capacity utilization.
What’s the fastest way to get accurate pricing?
Submit one consistent mini-SOW. Full Orbit uses it to match you with qualified providers and return 2–3 comparable quotes.