


Browse the latest capabilities that qualified buyers
are looking for on satsearch right now
| 1. MISSION PROFILE & PROGRAMMATICS | ||||
| PM-01 | Target Orbit Type | Determines radiation environment and link distance geometry. | Deep Space / Interplanetary | [Select Dropdown] |
| PM-02 | Design Life | Required operational duration in space environment. | 5 | Years |
| PM-03 | Flight Model (FM) Qty | Number of flight units required for spacecraft integration. | 2 | Units |
| PM-04 | Engineering Model (EM) Qty | Number of qualification/test units required for ground beds. | 1 | Units |
| PM-05 | Target Delivery Date | Required on-dock date for the first flight unit. | 30.09.27 | Date (YYYY-MM-DD) |
| 2. RADIO FREQUENCY (RF) PERFORMANCE | ||||
| RF-01 | Uplink (Rx) Frequency Band | Frequency band for receiving commands from ground/relay. | X-Band (8-12 GHz) | [Select Dropdown] |
| RF-02 | Uplink Center Frequency | Specific operating frequency if allocated by ITU/SFCG. | NA | MHz |
| RF-03 | Downlink (Tx) Frequency Band | Frequency band for transmitting telemetry and mission data. | X-Band (8-12 GHz) | [Select Dropdown] |
| RF-04 | Downlink Center Frequency | Specific operating frequency if allocated by ITU/SFCG. | NA | MHz |
| RF-05 | Min Downlink Data Rate | Minimum required throughput for science/telemetry data transmission. | 0.0001 | Mbps |
| RF-06 | Min Uplink Data Rate | Minimum required throughput for command uploads. | 0.0001 | kbps |
| RF-07 | Min RF Output Power | Minimum RF power output at transceiver antenna port. | 10 | Watts |
| RF-08 | Ranging Support | Indicate if coherent turn-around ranging is required for navigation. | Yes | [Select Dropdown] |
| RF-09 | Compatibility with NASA GSN | Compatible with the NASA Deep Space Network 34 m BWG stations for telemetry, telecommand and radiometric tracking as per DSN 810-005 Handbook. | Yes | |
| 3. SIZE, WEIGHT, AND POWER (SWaP) | ||||
| SW-01 | Maximum Allowable Mass | Strict allocation from the spacecraft mass budget. | <1.3 | kg |
| SW-02 | Envelope Dimensions (Max) | Maximum envelope allocation (Width x Length x Height). | 100x100x150 | mm x mm x mm |
| SW-03 | Primary Input Voltage | Spacecraft power bus nominal voltage standard. | 12 VDC | [Select Dropdown] |
| SW-04 | Max Power Consumption (Tx Mode) | Power draw when transmitting at maximum RF power. | <30 | Watts |
| SW-05 | Max Power Consumption (Rx Mode) | Power draw when in quiet listening/receive mode. | <10 | Watts |
| 4. ELECTRICAL & DATA INTERFACES | ||||
| IF-01 | Command & Telemetry Interface | Data bus protocol for standard spacecraft C&DH communications. | RS-422 / RS-485 | [Select Dropdown] |
| IF-02 | High-Speed Data Interface | Separate high-speed bus if required for payload data downlink. | RS-422 / RS-485 | [Select Dropdown] |
| IF-03 | RF Output (Tx) Connector | Physical RF connector type for the transmit line. | SMA | [Select Dropdown] |
| IF-04 | RF Input (Rx) Connector | Physical RF connector type for the receive line. | SMA | [Select Dropdown] |
| 5. ENVIRONMENTAL, RADIATION & QUALITY | ||||
| EQ-01 | Total Ionizing Dose (TID) | Minimum radiation dose hardness the component must withstand. | 30 krad (Standard LEO) | [Select Dropdown] |
| EQ-02 | SEE Immunity (LET Threshold) | Single Event Effect immunity threshold without destructive latch-up. | 37 | MeV·cm²/mg |
| EQ-03 | Operational Temp Range (Min) | Minimum qualification operating temperature limit. | -40 | °C |
| EQ-04 | Operational Temp Range (Max) | Maximum qualification operating temperature limit. | 85 | °C |
| EQ-05 | Component Quality Level | Required manufacturing, inspection, and component screening standard. | COTS+ / Rad-Tolerant | [Select Dropdown] |
| 6. SUPPLY CHAIN, LOGISTICS & RISK MANAGEMENT | ||||
| SC-01 | Export Control Jurisdictions | Regulatory framework governing hardware export/transfer (e.g., ITAR/EAR). | ITAR Controlled (USML) | [Select Dropdown] |
| SC-02 | Min Tech Readiness Level (TRL) | Minimum acceptable TRL to mitigate development risk. | TRL 8 (Flight Qualified) | [Select Dropdown] |
| SC-03 | Flight Heritage Verification | Requirement for exact or minor-variant hardware flight history. | Optional | [Select Dropdown] |
| SC-04 | Max Acceptable Lead Time (EM) | Maximum duration allowed from order placement to Engineering Model delivery. | 24 | Weeks ARO |
| SC-05 | Max Acceptable Lead Time (FM) | Maximum duration allowed from order placement to Flight Model delivery. | 32 | Weeks ARO |
| SC-06 | Country of Origin Restriction | Explicit exclusion or preference of manufacturing nations due to geopolitics. | NA | Text Entry |
| SC-07 | Obsolescence Management Plan | Requirement for a proactive component obsolescence & counterfeit mitigation plan. | Yes | [Select Dropdown] |
| SC-08 | Preferred Incoterms | Defines shifting of logistical costs, risks, and transport responsibilities. | FCA (Free Carrier) | [Select Dropdown] |
| SC-09 | Cleanroom Packaging Spec | Required cleanroom packing environment for delivery (e.g., ISO 7 / Class 10,000). | ISO7 | Text Entry |
We are seeking a complete ADCS solution for a 3U CubeSat Earth-observation mission scheduled for launch in Q1 2027. The ADCS must provide attitude determination and control suitable for a 3U platform operating in a 550 km sun-synchronous orbit (approximately 97.5° inclination).
The system should include the required ADCS hardware, sensors, actuators, electronics, flight software, and associated accessories required for integration into the satellite. We are particularly interested in a ADCS solution compatible with our 3U satellite architecture and capable of supporting detumbling, three-axis attitude determination and control, nadir pointing, and attitude stabilization during payload operations. The ADCS must have a GNSS as well.
The required performance includes a pointing accuracy of better than 1° (3σ), attitude knowledge better than 0.07°, and adequate attitude stability for multispectral Earth-observation imaging. The system should support integration with our onboard computer, and provide the necessary electrical, mechanical, software, and communication interfaces.
Please provide a complete technical and commercial proposal, including the recommended configuration, system specifications, interface requirements, integration requirements, software and licensing details, delivery schedule, and any additional components required for a complete flight-ready ADCS.
Schedule is critical: the satellite assembly must be completed no later than 30 December 2026, with launch planned for Q1 2027. Suppliers should therefore clearly state the earliest achievable delivery date and total lead time, including manufacturing, testing, and any required integration support.
Summary:
Payload:
Multispectral imager (VNIR, usually 4 to 7 bands, e.g. Blue, Green, Red, Red Edge, NIR), CMOS push-broom or snapshot
Attitude determination (ADCS):
Sun sensors (coarse on each face, one fine sun sensor)
Magnetometer (3-axis)
Gyroscope / IMU (3-axis MEMS)
Star tracker (needed for decent pointing accuracy when imaging)
Earth sensor
Reaction wheels (pyramidal)
magnetorquers (3)
| Technical Parameter | Unit / Format | Buyer Specification (Input Fields) |
| MISSION & ORBIT PROFILE | ||
| Mission Name | Text | Confidential 6U LEO mission (buyer anonymous via satsearch) |
| Target Launch Date | YYYY-MM-DD | 2028-02-01 (launch window Q1 to Q2 2028) |
| Expected Mission Life | Years | 1 year ground service (LEOP plus 12 months). Spacecraft design life 2 years. |
| Orbit Type | Dropdown | SSO |
| Orbital Altitude / Perigee | km | 550 (range 500 to 550) |
| Orbital Inclination | Degrees | 97.6 (sun synchronous at 550 km; 97.4 to 97.6 across 500 to 550 km) |
| TT&C UPLINK (COMMANDING) | ||
| Frequency Band | Dropdown | S-Band |
| Center Frequency | MHz | TBD, within 2025 to 2110 MHz (space operations allocation); assignment pending frequency filing |
| Modulation & Coding | Text | Per selected platform S band radio; CCSDS TC compliant (TBC) |
| Command Data Rate | kbps | 64 (TBC) |
| Polarization | Dropdown | RHCP |
| Minimum Elevation Angle | Degrees | 5 |
| TT&C DOWNLINK (TELEMETRY) | ||
| Frequency Band | Dropdown | S-Band |
| Center Frequency | MHz | TBD, within 2200 to 2290 MHz (space operations allocation); assignment pending frequency filing |
| Modulation & Coding | Text | Per selected platform S band radio; BPSK or OQPSK, CCSDS TM with standard coding (TBC) |
| Telemetry Data Rate | kbps | 128 (TBC) |
| Polarization | Dropdown | RHCP |
| Required G/T | dB/K | Station G/T shall close the TT&C link with 3 dB or more margin at 5 deg elevation. Supplier to state G/T. |
| PAYLOAD DATA DOWNLINK (HIGH-RATE) | ||
| Frequency Band | Dropdown | X-Band |
| Center Frequency | MHz | TBD, within 8025 to 8400 MHz. Please also quote S band high rate (2200 to 2290 MHz) as an alternate. |
| Modulation & Coding | Text | Per selected payload transmitter; OQPSK or 8PSK, CCSDS or DVB-S2 with LDPC (TBC) |
| Payload Data Rate | Mbps | 10 |
| Polarization | Dropdown | RHCP |
| Required G/T | dB/K | Station G/T shall close the payload link at the stated data rate with 3 dB or more margin at 5 deg elevation. Supplier to state G/T. |
| OPERATIONAL & PASS REQUIREMENTS | ||
| Target Passes per Day | Passes / Day | 4 |
| OPERATIONAL REQUIREMENTS | ||
| Min Pass Duration | Minutes | 5 |
| Geographic Preference | Text | Global network. Priority coverage region shared under NDA. Option: polar sites for TT&C. |
| Max Data Latency | Minutes | Supplier standard. Goal: 60 minutes or less. |
| DATA ROUTING, INTERFACES & SECURITY | ||
| Data Delivery Interface | Text | Secure SFTP or cloud object storage (e.g., AWS S3). Goal: REST API. |
| Protocol Standard | Text | IP based delivery or CCSDS SLE (TBC with platform supplier) |
| Encryption Standard | Text | Command authentication on TT&C. Option: AES-256 on payload data. |
| DERIVED MISSION METRICS (AUTOMATIC) | ||
| Est. Daily Payload Data Volume | GB / day | 1.5 |
Rideshare launch and dispenser for one 6U CubeSat, about 12 kg, to SSO (500 to 600 km, flexible). Spacecraft ready early 2028; launch window flexible Q1 to Q2 2028.
Please include: price including dispenser and integration services; available missions and windows in Q1 to Q2 2028; booking terms (deposit, payment schedule, cancellation and rebooking); what booking documentation you can issue within 4 weeks of signing; dispenser model and heritage; launch vehicle heritage; integration campaign location and duration; policy on provider caused delays.
Narrowband IoT store and forward payload for a 6U satellite in SSO (500 to 600 km), 2 year design life.
Key requirement: the payload must receive uplinks from standard 3GPP NB-IoT devices (Release 17 NTN). Proprietary protocols are not acceptable. Proof of concept scale: tens of ground terminals in one region.
Please also quote: 5 to 10 compatible ground test terminals, and an engineering model as an optional line.
Please include: architecture (SDR hardware plus NTN software stack, and who supplies each); supported frequency bands including 3GPP NTN bands; mass, volume, power, interfaces and antenna solution; software licensing terms; TRL, and if NB-IoT NTN is new on your hardware, what has been demonstrated and where; regulatory filing inputs available (spectrum masks, EIRP, G/T); export classification and country of origin.
Multispectral imager for a 3 axis stabilized 6U satellite in SSO (500 to 600 km), 2 year design life. Please quote two options: Option A: the widest swath you offer in a 6U compatible package. Option B: your best GSD that fits a 1U to 1.5U envelope. Please also quote an engineering model as an optional line. Please include for each option: GSD and swath at 500 km; spectral bands; SNR and MTF; envelope with and without enclosure (checking fit against a 96 mm bay); mass, power, data interface, data rate and onboard storage; calibration data delivered and support for alignment and calibration testing; TRL; export classification and country of origin.
| # | Parameter | Requirement | Response |
| 1 | Physical Properties | Payload Mass (kg) | Best estimate 3.0 kg (imager 2.0 kg; IoT payload 1.0 kg incl. antenna). Platform shall accommodate 3.75 kg (includes 25% system margin held by buyer). |
| 2 | Payload Volume (U or m3) | Best estimate 2.5U (imager 1U to 1.5U, 98 x 98 mm cross section; IoT payload 1U plus external antenna). Platform shall provide 3U payload volume. Please state maximum payload bay envelope. | |
| 3 | General | Payload type e.g. RF, EO (RGB, HS, MS IR) | Two payloads: (1) EO multispectral (MS) imager, nadir pointing; (2) RF narrowband IoT store and forward receiver supporting 3GPP NB-IoT (Release 17 NTN) |
| 4 | Desired orbits e.g. SSO, near-equatorial | SSO | |
| 5 | Desired altitudes e.g. 550 km | 550 km nominal; 500 to 550 km range. Up to 600 km only with orbit lifetime analysis showing debris compliance. | |
| 6 | EPS | Payload continuous power (W) | Best estimate 7 W orbit average (both payloads). Platform shall supply 9 W orbit average to payloads (includes 25% margin). |
| 7 | Payload peak power (W) | Best estimate 30 W peak (imaging and downlink concurrent). Platform shall supply 38 W peak to payloads (includes 25% margin). | |
| 8 | Payload duty cycle per orbit (%) | Imager 5 to 10% of orbit (target passes only). IoT receiver 10 to 20% of orbit (service region passes only). TBC at system definition. | |
| 9 | Payload voltage supply e.g. 3V3, 5V, 12V | 3V3, 5V and 12V regulated rails. Option: unregulated battery bus access. | |
| 10 | RF | High-speed downlink required e.g. > 5 Mbps? | Yes. 10 Mbps or more payload downlink (derived: 1 GB/day over 4 passes of 5 min = 6.7 Mbps, plus 50% margin). Please quote both S band high rate and X band options, with link margin of 3 dB or more at 5 deg elevation. |
| 11 | Daily data budget (Mb or Gb) | 0.35 to 1 GB per day | |
| 12 | Encryption required on TTC or payload data e.g. AES-256? | Command authentication required on TT&C uplink. Option: AES-256 encryption of TT&C and payload data (quote as a separate line). | |
| 13 | Interfaces | Bus to payload interfaces required e.g. CAN, I2C, SPI, UART, RS422, RS485, PPS | CAN (CSP) and/or RS422 for command and telemetry; high speed data interface for imager (LVDS or equivalent, per imager ICD); PPS required
|
| 14 | On-board data storage requirements? | 8 GB or more (7 days of maximum payload data). Supplier standard if larger. | |
| 15 | ADCS | Payload Pointing Modes when active e.g. Nadir | Nadir for imaging and IoT reception. Goal: off nadir target pointing. Sun pointing in safe mode and for charging. |
| 16 | Pointing Accuracy | Threshold 0.25 deg (3 sigma) during imaging. Supplier to state standard ADCS performance. Final value set after imager selection. | |
| 17 | Pointing Knowledge | Threshold 0.05 deg (3 sigma). Supplier to state standard ADCS performance. Final value set after imager selection. | |
| 18 | Slew Rate (°/s) requirements? | Supplier standard (nadir operations only; no agile imaging required). | |
| 19 | GPS required for position, velocity knowledge? | Yes (GNSS for position, velocity and time; needed for image geolocation and IoT timing). | |
| 20 | Propulsion | Propulsion Required? | No. Option: quote a deorbit assist or collision avoidance line item. |
| 21 | Propulsion type requirement e.g. electric, chemical? | N/A (if optional line quoted: electric or cold gas, supplier to propose) | |
| 22 | Propulsion system use e.g. orbit maintenance | N/A (if optional line quoted: collision avoidance and deorbit assist) | |
| 23 | Propulsion thrust or delta V requirements? | N/A (if optional line quoted: supplier to state available delta V) | |
| 24 | Operations | Operations duration e.g. 6 months, 12 months | LEOP plus 12 months nominal operations; 2 year design life |
| 25 | Summary of payload operations or CONOPS? | Imager acquires multispectral scenes over target regions and stores onboard for downlink via commercial ground stations. IoT receiver collects uplinks from standard NB-IoT ground terminals over one service region, stores and forwards via the payload downlink. S band TT&C. Sun pointing safe mode.
| |
| 26 | Other | Any other comments or notes? E.g. ITAR restrictions, ground station requirements. | No ITAR content. Please state export classification (ECCN) and any US origin content. For each heritage claim, please state what differs from the flown configuration (hardware, software, environment). Ground segment via commercial ground station service. Please also quote: FlatSat / EDU kit with EGSE; protoflight environmental test package (vibration, TVAC, EMC, magnetic characterization); supplier engineer support for final integration at a customer facility (day rate); LEOP and commissioning support.
|
| 27 | Other | Anything else? E.g. budgetary or lead time requirements. | Budgetary (ROM) figures requested by Tuesday, September 29, 2026. Order expected Q1 2027; platform and FlatSat delivery by Q3 2027. Please state lead time, payment milestones, quote validity, and flight heritage (mission names and launch years).
|
RFI for alternative to Explosive bolts for use in a separation system.





























































































