Getting Started¶
CubeSats are satellites in the nanosat class built around established design specifications (the CubeSat Design Specification, or CDS). The basic “1U” CubeSat is a 10×10×10 cm cube. These standardized form factors use common deployer hardware, which lowers the cost of development and launch, making access to space more attainable – even for small teams or individuals. It’s important to note that launch provider capabilities and requirements may deviate from the CDS and will ultimately determine the allowable volume and weight of the satellite.
This section is for those new to CubeSats or small satellite development. It gives you a broad overview of what CubeSats are, what goes into building one, and where to begin your journey.
Where to Start¶
- NASA's CubeSat 101 is a great beginner-friendly overview of CubeSat design and mission planning, and a highly recommended starting point.
- The CubeSat Design Specification (CDS), maintained by Cal Poly, provides the official framework for CubeSat form factors. Reading through it helps you understand the physical and operational constraints of a CubeSat mission.
- Check the Wikipedia page for some history and context.
- For a general intro to the New Space economy, this course by EPFL on edX is a good place to start.
- Nano Avionic's CubeSat 101 provides a brief, high-level overview.
- To keep up to date with the space economy and space research at large, subscribing to the Orbital Index is highly recommended.
- If you're building a company and looking to hire people, Space Crew is a good place to start.
- Shameless plug: I am developing an open source CubeSat and documenting the process on YouTube. You may find this relevant: Build a CubeSat Channel.
Development Flow¶
CubeSat projects usually fall into one of two categories: either you have a specific goal to achieve in orbit (e.g. a business case), or you're part of an academic program where the learning process is just as important as the outcome. In either case, it’s important to think of all parts of a CubeSat mission holistically, as they are interdependent:
Project Phases¶
- Feasibility Study
- Fundraising
- Mission Design and Development
- Launch Provider Procurement
- Flight Segment Design and Development
- Ground Segment Design and Development
- Mission Insurance Procurement (optional)
- Regulatory Approval
- Assembly, Integration and Testing
- Launch
- Operations
Milestones¶
- Feasibility studies completed
- Funding is secured
- Preliminary Design Review (PDR) completed
- Critical Design Review (CDR) completed
- Flight/qualification hardware procured
- Flight/qualification hardware tested
- FlatSat testing completed
- Functional tests performed at system level
- Environmental tests performed at system level
- Launch service provider selected and contract signed
- Mission insurance policy secured (optional)
- All regulatory approvals granted
- Flight ready
- Launch opportunity is secured
- Launched
- Commissioned
- Entered Nominal Operations
- Passivated
- Deorbited
Note
A full CubeSat development project typically takes 1-2 years or more from initial planning to launch and operations. That includes everything from prototyping and documentation to regulatory approvals and environmental testing. Most likely, the process will not be linear, and different aspects of your system will be in different stages.
If your CubeSat mission is result-oriented, you probably have a payload that needs to reach orbit and send data back. In that case, it's advisable to source a bus with flight heritage – i.e. structure and subsystems that have been flight-proven – from an established vendor. Check out SatSearch and CubeSat Shop for help with sourcing.
If your mission is process-oriented, you’re more likely to build a large portion of the flight segment yourself. This is absolutely feasible, but the process tends to be more iterative and may involve more work in integration, qualification, and testing. It’s common to build a FlatSat or engineering model first – a functional layout of all your subsystems on a testbench – for easier debugging and early verification.
Launch Provider Procurement¶
Starting the process of finding a rideshare opportunity early will help you align with your launch provider’s requirements, avoid costly redesigns, and fully leverage their support offerings. The CDS provides a guideline, but the launch provider’s specifications always take precedence.
A common path to orbit is via a SpaceX rideshare mission, often coordinated through a launch services provider like Exolaunch.
Note: Once you’re booked on a mission, launch integration begins. You’ll need to meet all interface and safety requirements and typically deliver your flight hardware well in advance – anywhere from 1 to 6 months before liftoff. If your CubeSat isn’t ready, it simply won’t fly.
Regulatory Approval¶
Regulatory approval depends on your location, your launch provider's location, and what you intend to do in orbit.
Warning
Nothing on this site is legal advice. You will need to familiarize yourself with your countries legislation, rules and best practices around launching and operating a CubeSat.
Radio Frequency Usage¶
The most common way to communicate with a CubeSat is via UHF in the 430–440 MHz band. Someone on your team must hold an amateur radio license (HAM) or a Commercial Operator License. This person is responsible for compliance with national and international regulations.
At a minimum, you’ll need authorization from your national regulatory body (e.g. the FCC in the USA). If you're using amateur bands, you’ll also need coordination through the International Amateur Radio Union (IARU). Generally, either the IARU or your national regulator will handle coordination with the International Telecommunication Union (ITU). If you use non-amateur bands, you may have to file with the ITU directly.
If required approvals aren't in place by launch day, your CubeSat will not be allowed to deploy. Start the licensing process early.
Remote Sensing¶
If you plan on performing Earth Observation (EO) with cameras or sensors, you may require a remote sensing license from a national body such as NOAA in the USA.
Mission Operations¶
Once your CubeSat is deployed into orbit, you’ll begin the commissioning phase: acquiring the signal, establishing contact, and checking that all subsystems are operational. After that, your mission enters its operational phase – collecting data, sending commands, and maintaining the satellite. Plan time and resources for this part too: missions can last anywhere from a few months to several years, depending on your orbital lifetime and system performance.
Communities & Learning Resources¶
- CubeSat Resources – Head over to the main content to start learning.
- r/CubeSats – Active Reddit community.
- SatNOGS – Open-source satellite ground station network.
- Build a CubeSat Discord – Community focused on open-source hardware and software in CubeSat development.
- NASA CubeSat Launch Initiative – If you are based in the USA, NASA may help you get your CubeSat launched.
- ESA Fly Your Satellite! – Resources, events and support for CubeSat devs based in an ESA member state.