This project focuses on programmable AI processing in orbit.
The MOI family includes MOI-TD, MOI-1 lost during launch in January 2026, MOI-1A and the planned MOI-1B. Current TakeMe2Space mission history and technical article both report successful MOI-TD AI-lab operation, including on-orbit inference. An older undated data sheet conflicts and is retained as superseded historical evidence, not the current project outcome. D-Orbit confirms MOI-1A deployment on October 14, 2026, and TakeMe2Space now reports MOI-1A lost in orbit. The loss date and cause are undisclosed.
Scope: Shared computing & storage · A shared computing or storage platform, or a program developing that infrastructure. Classification describes intended use, not operating capacity.
Observed on an undated operator page on September 26. Numerical precision is unspecified; this is not a demonstrated benchmark or failed MOI-1 capacity.
Operator technical account of the launched demonstrator with unspecified arithmetic precision. Current operator mission history and technical article report successful AI-lab protocol execution and in-orbit inference. The 4 TOPS value is an advertised hardware specification, not measured orbital throughput. An older undated data sheet is retained as superseded historical evidence. This is separate from the planned MOI-1A 117 TOPS specification.
Undated operator technology page read completely on September 29. The MOI-1A specification states 2 TB; the separately configurable 4 TB AI-Cube option is not established as this mission configuration. Planned hardware capacity, not deployed or measured in-orbit storage.
6 satellitesPlannedTotal planned MOI constellationEvidence & scope
RIDE!'s September 10 release describes a total six-satellite constellation and says its contracted pair forms part of that total, with the pair targeted for Q3 2028. The operator homepage's older Q4 2027 network target conflicts with this schedule; overall constellation completion remains unresolved. The pair is not additional to the six, and no deployed count is established.
Figures retain their disclosed units and scope. Launched hardware does not establish demonstrated performance; targets may change. Not disclosed means no figure in the reviewed sources.
Falcon 9 Transporter-18 launched ION carriers whose manifest lists MOI-1A via Impulso Space.
Carrier launch and subsequent October 14 deployment are supported. No direct TM2S–SpaceX contract, spacecraft contact or computing result is established.
Announced 1 Oct 2026 · Evidence checked 27 Oct 2026
Launch management for two TakeMe2Space constellation satellites targeted for Q3 2028, including satellite integration, verification, regulatory compliance and oversight of the launch campaign.
Signed launch-services agreement; contract value is undisclosed. These two satellites form part of the planned six-satellite constellation. The primary release does not name Waymaker-2, SpaceX, SEOPS, spacecraft power or hardware configuration and does not cover the MOI-1A replacement launch.
Announced 10 Sept 2026 · Evidence checked 28 Sept 2026
Joint ground demonstration of Little Place Labs' ORBITFY preprocessing and application software on TakeMe2Space's OrbitLab ground test platform under an announced demonstration agreement.
The release carries a February 25, 2026 announcement dateline and March 3 publication metadata. Pilot missions, orbital deployments and commercial agreements are conditional on future mutual alignment. No paid in-orbit service, procurement buyer, price or completed demonstration outcome is established.
Announced 25 Feb 2026 · Evidence checked 28 Sept 2026
MoU for intended integration of AICRAFT Pulsar Development Kit, SpaceWire-enabled Pulsar and NEXON Edge AI Server equipment into TM2S’s planned OrbitLab constellation from 2026.
Disclosure date, not exact signing date. No paid order, fixed volume or completed integration established. OrbitLab is not a new duplicate project.
Announced 1 Oct 2025 · Evidence checked 13 Oct 2026
ISRO PSLV-C60 launched the MOI-TD payload on December 30, 2024; POEM-4 hosted the payload and provided its orbital platform.
This is an explicitly identified delivered launch and hosted-platform role. The data sheet is undated; December 30 is the launch date, not an agreement date. No direct buyer, procurement instrument, price or paid-service contract is disclosed. Current operator records report successful MOI-TD AI-lab operation, including in-orbit inference. The data sheet's conflicting outcome account is superseded historical evidence.
Announced Publication date not supplied · Evidence checked 27 Sept 2026
MIRA Earth-observation imaging payload integrated aboard TakeMe2Space's MOI-1 satellite for the PSLV-C62 mission.
The official website is undated. Integration is established, but the failed PSLV-C62 mission does not establish orbital qualification or operation. No separate MOI-1A procurement is inferred.
Announced Publication date not supplied · Evidence checked 20 Oct 2026
Operator targets MOI-1B for November 2026. Launch and results remain unconfirmed. The exact date and cause of the MOI-1A loss remain undisclosed.
Manual review with evidence gaps 29 Oct 2026. Current operator records support successful MOI-TD AI-lab operation. The older undated data sheet is retained as superseded historical evidence. Separate MOI-1A loss details and network schedule conflicts remain limited-profile questions. Primary body last observed 23 Oct, 06:37 UTC. Source monitoring: ongoing. Source collection and substantive profile review are separate checks. Plans and dates may change.
D-Orbit confirms MOI-1A deployment on October 14 after the October 1 carrier launch. The current operator mission history reports MOI-1A lost in orbit. Exact loss date, cause and any earlier contact, commissioning or AI workload results remain undisclosed.
The operator homepage targets a total six-satellite network by Q4 2027, but RIDE!'s September 10 and 17 releases place two satellites explicitly belonging to that constellation in Q3 2028. The network completion schedule remains inconsistent. These two are not additional to the six; the older data sheet's post-MOI-1A wording does not establish seven spacecraft.
117 TOPS is an advertised GPU specification without disclosed arithmetic precision or an in-orbit benchmark.
D-Orbit identifies Impulso Space as intermediary for MOI-1A. Direct legal purchasing chain and value remain undisclosed. RIDE! covers two later satellites, not this flight. Customer utilization and revenue remain unverified.
The technology page mixes MOI-1 and MOI-1A descriptions and advertises 120 W peak/payload allocation, 67.2 W peak solar generation and a 200 Wh battery alongside continuous-operation language. Sustained compute power and duty cycle are not demonstrated by these design figures.
Current TakeMe2Space mission history and technical article report successful MOI-TD AI-lab operation. An older undated data sheet conflicts and is retained as superseded historical evidence. Exact source revision dates and exact mission duration are not disclosed and are not treated as current performance facts.
Project updates
Verified announcements and milestones linked to this project, newest first.
The New Indian Express reports that TakeMe2Space’s MOI-1A spacecraft deployed after Dhruva Space’s LEAP-2 on SpaceX’s Transporter-18 mission early on October 2, Indian time. MOI-1A is designed to process Earth-observation data onboard using an Nvidia Orin NX-based system.
Punjab Newsline reports that TakeMe2Space’s MOI-1A orbital-computing satellite launched aboard SpaceX’s Transporter-18 rideshare mission. The spacecraft is designed to process imagery and other data in orbit and downlink selected results instead of all raw data.
India Today reports MOI-1A is scheduled for SpaceX’s Transporter-18 mission on October 1. TakeMe2Space’s mission page still labels the replacement mission as tentative for October. Flight, payload deployment and commissioning remain unconfirmed.
Reuters reports TakeMe2Space said MOI-1A had 23 signed customers, carries Nvidia Orin NX processors and uses about 150 watts. The company described the sub-50 kg mission as onboard edge computing and identified agriculture, mining, supply-chain, insurance, GIS and education users.
RIDE! says it contracted more than one metric ton of smallsat launch capacity for 2028, naming SatVu, NewOrbit and TakeMe2Space among its customers. The release places TakeMe2Space in a Q3 2028 launch group and says RIDE! manages rideshare capacity across multiple launch providers.
The signed contract covers integration, verification, regulatory compliance and launch-campaign management for two satellites targeted for Q3 2028. TakeMe2Space identifies the pair as part of its six-satellite constellation. The release does not name the launch vehicle or disclose a contract value.
IIIT Hyderabad CIE published the Transporter-18 replacement opportunity in its April newsletter on May 4. This is the newsletter publication date; the underlying agreement date is not disclosed.
The release, carrying a February 25 announcement dateline and published March 3, describes an agreement to test ORBITFY on the OrbitLab ground platform. Subsequent pilot missions, orbital deployment and commercial agreements are conditional; completed orbital service is not established.
Current TakeMe2Space mission history reports success and more than 20 experiments, while the current technical article reports nominal AI-lab protocol execution and a camera saturation fault. The older undated data sheet is retained as superseded historical evidence. Exact revision dates and mission duration remain undisclosed.
MOI-TD flew on PSLV-C60/POEM-4. Current TakeMe2Space mission history and technical article report successful AI-lab protocol execution and in-orbit inference. An older undated data sheet is retained as superseded historical evidence. Exact mission duration remains undisclosed.
Undated technology page identifies a 6U, 14 kg MOI-1B with 117 TOPS advertised compute and 2 TB storage, targeting November 2026. Not evidence of launch, commissioning or a correction to the separately deployed MOI-1A.
The current undated operator mission history labels MOI-1A Lost in Orbit and reports loss for all purposes. It supplies no loss date or cause. D-Orbit’s confirmed October 14 deployment remains part of the mission history.