Giving an AI agent its own private key is one of the riskiest security decisions you can make right now. A private key allows software to sign transactions for you, and researchers have already tricked AI agents into signing transfers to wallets the researchers controlled. A key management service (KMS) keeps keys locked away and still allows agents to use them, without ever having full access to the key itself. There's 3 critical reasons your agents need a KMS that is actually secure👇 1. A tricked agent can't leak the key if it never has full access to it 2. Limits live at the key level, so when you set a limit like "never send more than $500" the agent cannot bypass this limit 3. Hardware-isolated environments (like TEEs) let you verify where signing happens instead of trusting a server As agents get more capable, a trusted KMS is how you decide what they're actually allowed to do. We see this as critical infrastructure to the future of the space internet. More to share on this soon 👀

Post Quantum Cryptography (PQC) is critical infrastructure for space technologies. And this is a much deeper conversation than just preparing for the inevitability of quantum computers breaking classic cryptographic encryption. We need to build adaptable, software-enabled post-quantum migration solutions for spacecrafts that work with data in any capacity. At SpaceComputer, PQC readiness and migration is a top priority amongst our cybersecurity solutions. Subscribe & watch the full video on YouTube: piped.video/oa4zc0JiwH0

Post-quantum migration is fundamentally a key management problem. You can’t upgrade key security if you can’t find the keys. A key management service (KMS) centralizes key generation, storage, access control, rotation, and audit, so keys live in one hardened place, like a trusted execution environment (TEE). That's security you need today. Post quantum cryptography (PQC) is security for the future where quantum computers will eventually break public key encryption. These threats are relevant today. Harvest now, decrypt later attacks collect encrypted data today to break it once quantum machines are strong enough. So why do you need both? When every key lives in a KMS and you swap in quantum-resistant algorithms, every key inherits the upgrade. The KMS becomes your layer of cryptographic agility. A KMS also automates the mechanics of generating new keys, re-encrypting data, and key rotation and retirement across your stack. It also absorbs the friction of PQC's larger keys and signatures so your applications stay fast. With quantum computing still on the horizon, and KMS options available from every cloud provider, why is SpaceComputer building a post-quantum agile platform? One simple reason: a satellite launched today must be ready for the next 5-10 years. You can't add hardware in orbit (for obvious reasons), so crypto-agility must be built in before launch. Our KMS will anchor keys in attested TEEs, non-exportable by design: they can be used but never extracted. We're starting with hardened infrastructure on Earth, eventually moving to keys born in orbit inside a satellite-based TEE, with post-quantum readiness currently in development. So we ask you: how are your security keys managed today? And if you could test a KMS built for orbit: would you? Drop a 🙋 below if you'd want early access.

Post-quantum cryptography changes the math that supports your security without changing how it works on the surface. You'll still have a private key and a public key. The algorithms are migrated within a key management service to withstand quantum computers, not just classical ones. @rezabfil breaks it down in the clip below 👇

If your satellite isn't secure at launch, it can be compromised with as little as a software-defined radio and a few software bugs. "So we have to consider the life cycle and the lifetime of the designs of the respective choices, the respective spacecrafts and make sure that there are solutions for that." That's our mission at at SpaceComputer: building secure satellite computing systems for the long term, starting at the hardware and software level. Catch the full deep dive with on YouTube: piped.video/mip1p4zy3Ks

Watch the full episode of the Space Show here: piped.video/watch?v=Lrim_L9b…

Every spacecraft and ground station in the data chain needs security and end-to-end verifiability. One of the best use cases for this is satellite imaging. Our approach to this is to use cryptographically verify what image came from which satellite. This high-security guarantees help prove the image wasn't tampered with, which is useful for providers and data users alike. Let us know in the comments what other use cases verifiability in orbit could be used for? 🤔

For some applications, the most secure place to run a computer is where nobody can reach it. For others physical inaccessibility is the biggest limitation. We spend a lot of time thinking about these kinds of tradeoffs that come with building compute systems in orbit. On Earth, compute is abundant and trust is the hard part. Roughly 55% of data center security incidents come from the inside. In orbit - nobody can access the satellite, and therefore the physical attack surface is ≈0. In orbit, that same isolation means no repairs, radiation-constrained chips, and a power budget where one satellite roughly equals one GPU today. So which one do you build on? It depends on what applications you're building for and the level of in-depth security you need. If physical possession of the hardware is part of your threat model, orbit offers guarantees Earth can't match. If you need fast, large-scale compute, and your threat model is handled by conventional controls, Earth wins on practicality. (For now). So where do you sit on the tradeoffs of physical isolation and capabilities on Earth versus on orbit? Let us know in the comments 👇

Ready for the full talk? Subscribe to the Frontier Podcast on YouTube: piped.video/mip1p4zy3Ks?si=CMvD…

At SpaceComputer, we look at our open infrastructure the way the internet once looked at Linux. Linux infrastructure is open, auditable, and vendor-neutral. That openness is why it’s the foundation of the internet: hyperscalers, competitors, and governments could all standardize on it, because trusting Linux never meant trusting a vendor. We're doing the same for the space internet. Our infrastructure design, Space Fabric, is built on open verification. We publish our tech stack and system design, and work with hardware partners like Tropic Square also take an open source approach. We incorporate Raspberry Pis into our infrastructure due to their exceptional interoperability across diverse applications. Linux was one of the biggest companies to build backbone level verifiable infrastructure into what it is today. The space internet needs the same foundation, and we're building it. Explore the solutions we offer now: spacecomputer.io/solutions/?…

The space sector inherited so much of its culture from government bureaus, where information was gatekept. That culture is changing fast, and we're ushering in a new spirit to the space sector. Our choice to build open source infrastructure in orbit is a choice that has left people puzzled. Everything about the space industry incentivizes keeping the tech in a walled garden. 3 reasons companies choose close source: 1. Protect expensive IP 2. National security laws & compliance 3. Control every detail of the system All three concerns come down to the same question: who holds system data, and what happens if that data ends up in the wrong hands. Cryptography changes this calculation by adding verifiability and encryption. For comparative reference: your bank publishes which encryption standards it uses and keeps your keys secret, and the same logic applies in orbit. Satellite-based TEEs and cryptographic attestation lets the customer verify while everything else stays confidential. Being open source is a choice that shapes how we operate: a development process distributed across the world, deliberate decisions about which components we pick for our stack. Head to the full podcast episode on our architecture: piped.video/mip1p4zy3Ks

This Sunday, August 16th, Co-Founders @semicondurian and @rezabfil are joining @SpaceShow with Dr. David Livingston! We'll be discussing how SpaceComputer is building the secure space internet: satellite-based TEEs, Space Fabric, and why the next generation of spacecraft needs credibly neutral, interoperable infrastructure. The Space Show is live with questions, so show up ready to ask yours! Tune in on Zoom at 2 PM PDT / 5 PM ET: thespaceshow.com/show/16-aug…

As the space internet emerges, so do its applications. Onboard AI processing of Earth observation (EO) data. Satellites connecting directly to your phone. Today, connectivity inside a single constellation is possible, but between different vendors, they don't link. Connectivity across services is a goal at this stage. Reaching it will be critical to offer secure services from orbit the same as we do on Earth. Here's how a secure system would complete a user's request: A query enters through an API for analyzed EO data. A ground station finds an available satellite, books the contact window, and translates the request into a signed task. The EO satellite captures the imagery, then passes the data to a compute satellite. Onboard AI would extract the answer inside a trusted execution environment (TEE), with attestation verifying what code ran. Only the results are downlinked back through the ground station to the user. This connectivity and interoperability is what will make the space internet comparable to Earth internet. As more spacecraft and active satellites head into orbit, we need applications that connect securely end to end across satellites, ground stations, and everything in between. Where do you think in this process will have the biggest challenges with reaching Earth-level capacities? 🛰️

By not considering security now, you are sending obsolete infrastructure to space. Space compute is accelerating, and as @semicondurian says, the signal for robust secure compute in space is highlighted by 2 space trends: 1. more complex compute systems 2. more cyber warfare @rezabfil: "Use AI as an example. When a general user wants to interact with the infrastructure, it opens the attack vector massively. You make to make sure systems are built with this in mind. It wasn't like this in the past...the barrier to entry was high, and you needed to be a state-level attacker to access the domain...now it's a matter of a software-defined radio and a couple of bugs to access it." As barrier to entry lowers, more infra moves to space, and we must look for solutions for the threats that will arise in the future, especially for the missions flying for 2030 and beyond. Tune into the rest of the conversation with Frontier Pod host @ideacasino on building secure multi-purpose space infrastructure: piped.video/mip1p4zy3Ks

After 6 months it's finally time... the next episode of the Frontier Pod is live! 🚀 We had none other than @rezabfil on to discuss how to build space internet infrastructure, and SpaceComputer's most recent architecture development: Space Fabric. On this episode we dive into what it takes to build for a future with orbital compute and multi-purpose satellites applications, instead of siloed, single purpose satellites. Subscribe and watch the full episode on YouTube: piped.video/mip1p4zy3Ks

What is one of the strongest binding elements for connectivity between layers of internet infrastructure in space? Operations. Similar to enterprises, without interoperability, the operational capabilities between service layers remain siloed. It limits usability and decreases the output of what you can get in terms of services. We're working to eliminate that for the space internet. As we discussed previously, there are six layers to space internet infrastructure (what we're working to build). Those are: 1. ground stations 2. communications 3. compute 4. data 5. analytics 6. security Operations tie everything together. We're connecting each layer using Orbitport: our secure gateway for orbital services. Orbitport handles the operations that satellite infrastructure demands. ✅ Scheduling and prioritizing satellite passes. ✅ Buffering batched data in short contact windows. ✅ Routing data from ground stations into one processing pipeline. ✅ Verifying signatures so data integrity holds from satellite to consumer. ✅ All services accessible through one API. What this means for space operators is they can all use a new provider or payload without changing your stack or code. That's operations across different layers of space internet infrastructure, handled in one place. Learn how the architecture works in our docs: docs.spacecomputer.io/docs/c…

Interoperability and connectivity are the two things stopping space internet infrastructure from scaling to meet space services needs on Earth. We're building within each of these layers to solve to solve that blockage. Here's how the different layers of the stack work, and how we can start connecting each of them: blog.spacecomputer.io/6-laye…

@rezabfil presenting our Space Fabric architecture paper Currently at Science of Blockchain Conference

What is one of the biggest problems we're seeing in space tech today? Siloed services and resource scarcity. This is even the case for getting a launch slot on a SpaceX rocket. There's a massive increase in demand to have access to space, but everyone is building for one use, or one customer. And these purpose-built siloes mean EVERYONE has to launch their own satellite. We believe that shouldn't have to be the case. By building interoperable and multi-purpose infrastructure that can be (securely) on board any satellite, any satellite can improve resource utilization and have more than one customer. It also provides improved connectivity between available services and different systems (e.g., communications, compute, intelligence, Earth observation). The real question is: how should these interoperable and multi-purpose systems be secured? Thoughts in the comments 👇 Video credits: Cysat conference

The SpaceComputer team is heading to Stanford for the Science of Blockchain Conference next week! @rezabfil will be speaking on Space Fabric, SpaceComputer's secure orbital computing architecture, and the cryptography that powers our security mechanisms. 🗓️ Talk is on July 28th at 10:45 a.m PT. Co-Founder @semicondurian and Advisor @dahlia_malkhi will also be in attendance, come talk to us about cryptographically secured compute in space!

Right now, one satellite = one user. In most cases, that one user is one organization, where proprietary designs for one application don't take into account the need for interoperability between layers of infrastructure. In the growing space economy, infrastructure that can connect to different providers for internet services like communications, compute, and data is becoming a bottleneck. That connectivity is what's currently missing, and is being built for the space internet at scale today. Tune into @rezabfil for the downstream effects of the interoperability bottleneck:

How many layers of the space internet tech stack do you think have emerged? We see six. Ground stations move data between Earth and orbit. The comms layer carries it between satellites. The computing layer processes it where it's generated. More compute is moving to space in the next decade. The data layer stores and routes it. More data is moving to space with compute and increase in satellite usage globally. The analytics layer turns it into intelligence, processed via the compute layer. And the security protects all processes from bad actors. Connectivity gets most of the attention when you say 'space internet.' A functioning space internet, similar to Earth internet infrastructure, needs every layer operating together. Today, each of these layers is being built by teams working on different stacks, that may or may not be interoperable. That's why adaptability matters as much as capability. Infrastructure for the space internet has to plug into each layer, whichever stack it lives in. We built Space Fabric to integrate vertically across the stack, with security and post-launch adaptability in mind Drop a follow to see how all these layers interoperate! 👀

We’re proud to announce SpaceComputer has partnered with @tropicsquare to integrate TROPIC01 into our hardware design for Space Fabric architecture. TROPIC01 is publicly auditable, which makes it a natural fit for an architecture designed around verifiable trust in orbit. We’ll be taking it into space for the first time in upcoming 2027 missions! For more partnership details: blog.spacecomputer.io/spacec…

As the orbital economy is built out over the next 5-10 years, we need to rethink the infra stack that supports space-based services and applications. How we see it: we need an open infrastructure standard similar to Cloudflare or Raspberry Pi. This means services can be built on top of a secure and interoperable tech stack, rather than several disjointed and proprietary infra stacks. That's the goal of SpaceComputer's space internet infrastructure stack. Watch the full talk by Co-Founder and CEO @semicondurian on YouTube: piped.video/5TWNQ8d7CBM?si=PGE3…

It started with the AI boom. Then we saw space tech go mainstream with the SpaceX IPO and rise of the orbital data centers. What comes next? The layer that connects all components of the different space technologies in orbit: The Space Internet. We believe that the space internet needs an secure, interoperable, and standardized infrastructure layer to build on top of. Watch the full talk by SpaceComputer Co-Founder and CEO @semicondurian here: piped.video/5TWNQ8d7CBM

Three quantum problems space tech is solving right now (not later). Quantum in space gets framed as a future threat for many industries, but the satellites and spacecraft heading into orbit this year will need to have post-quantum readiness plans in place. Quantum computing brings new developments across security in space. Here's 3 areas entrepreneurs are actively working on solving: 1. Post-quantum cryptography, moving from standards to flight hardware 2. Satellite QKD, going from lab demo to real networks 3. Quantum sensing, opening navigation beyond GPS The solutions are being built now. What areas are you keeping an eye on?

Post quantum cryptography standards are yet to be tested against time. As quantum computing evolves, so do the approaches to mitigating threats. The most important parts of post-quantum readiness plans, especially in space tech, are agility and being able to upgrade software and hardware as needed.

The SpaceX IPO will usher in the next phase and expansion of space tech, creating a root of trust beyond contracts for an emergent, modular, and interoperable space economy. At SpaceComputer, we're building the trust layer for space.

As launch and connectivity in orbit mature, the frontier moves compute, data, and the systems that make them secure and verifiable. The next layers will be built by new space startups, rather than restricted to governments and legacy organizations.

Further, SpaceX's reusable rockets have caused a 20x drop in the cost of reaching orbit, reliable access to space is now a foundation the whole industry can build on.

The largest IPO in history is bigger than one company. It marks the moment space became a highly investable category, with up to a trillion dollars of capital expected to follow into the sector.

What does the SpaceX IPO mean for new space infrastructure? 🧵

Your KMS is only as strong as the cryptographic algorithms protecting it. Most KMS infrastructure relies on ECC and RSA, both vulnerable to Shor's algorithm on a quantum computer. NIST has standardized the PQC replacements: ML-KEM, ML-DSA, SLH-DSA. For satellites, the timeline is compressed. Hardware in orbit cannot be re-keyed. We designed SpaceComputer KMS to be algorithm-agnostic from day one. Learn how PQC and KMS fit together ↓

From January to August in 2025, ~117 cyber incidents targeting space systems were reported, up 118% from the same period in 2024. And one of the attack surfaces that are easiest to access from Earth? Ground stations. Ground station security is one of the first layers of space infrastructure that needs cybersecurity measures in place, as they are the direct connection point to satellites in orbit. We created a comprehensive breakdown of ground station cybersecurity, and strategies for threat mitigation. Link below👇

It takes less than 11 hours to prove a satellite is genuinely in orbit. You do it once, with multiple ground stations on Earth, and it holds for the satellite's entire life. 🧵

Our satellites will have an unspoofable “caller ID.” All it takes is a protocol that runs once, and can be verified for the course of its lifetime. We use a network of ground stations to run a challenge–response handshake as the satellite does its first passes in orbit. When enough stations independently verify it and reach consensus, the satellite is certified. Then ground stations know what satellite they're talking to overhead.

Most of the security the tech you use every day relies on one thing remaining a secret: a signing key. Often referred to as a private key, secret key, or signing key, they are what a computer system uses verify it is who it says it is. A few examples you might be familiar with: 🔑 Browser security (TLS/HTTPS) 🔑 Signed software updates 🔑 Digital signatures These work because one key stayed secret and only the real system or system's owner could use it. So here is a fair question to ask about any platform you're working with: where was that signing key created, and who had access to it before it reached you? We wrote up what a signing key is, and why generating them in space changes trust systems. blog.spacecomputer.io/what-i…

If locksmith copies your house key. And they promise they destroyed the duplicate. And you have no way to verify. Do you trust them? That's a vulnerability so many secure compute modules like TEEs face. Now imagine that level of trust in a satellite you can never double check after launch...especially if you don't have verification set up. If satellite signing keys are generated on Earth by the manufacturer, sometimes years before launch, there's a gap in time for a pre-launch attack. So when designing our security mechanisms, we engineered around this vulnerability. Every SpaceComputer signing key will be generated after launch, on the satellite's first boot in orbit. No human or manufacturer on Earth ever holds the keys. For customers evaluating orbital compute platforms, which is preferred: trusting a vendor's claim and contract, or verification from the hardware itself?

SpaceComputer handles signing key genesis differently. A 'key' layer of security we offer: all signing keys are generated after reaching Low Earth Orbit. They were never on Earth, and never left in the contractual trust of the manufacturer. And all compute tasks are secured without a single point of failure, through two key pairs, one for each co-processor onboard the satellite. In orbit, we believe security is a priority, and never a compromise. 🛰️ @rezabfil outlines the post-launch process👇

By 2027, several orbital compute platforms will be in production. Most will depend on a single compute chip vendor never being compromised. Once a satellite is in orbit, there isn't an easy fix to swap out a compromised chip. The four hardware components that show up in our conversations around orbital security are: → Secure Elements (SEs) → Trusted Execution Environments (TEEs) → Trusted Platform Modules (TPMs) → Hardware Security Modules (HSMs) Each hardware component has a different purpose. Whether a system can be independently verified depends on its hardware architecture and the manufacturing supply chain (aka who builds these pieces). SpaceComputer's satellites will use: → Two secure elements from different vendors → All signing keys generated after orbital deployment → TPM is on the on-board relay, and provides security and a future PQC integration point. The term "hardware root of trust" means exactly what it says. The trust is in the hardware. If the hardware is compromised, the rest of the stack has nothing to fall back on. That is why every architectural choice is considered for if the system can be trusted or not. Our paper, Space Fabric has the details: spacecomputer.io/spacefabric

No SpaceComputer signing key has ever existed on Earth. The secure elements on our satellites only generate their security keys after launch. Two secure elements (chips) from different companies, and both must sign to certify. @rezabfil walks through the architecture: piped.video/03KnXUYraWc

"We're trying to make user interaction (with space infrastructure) more unified and streamlined and also secure end to end." That's why we're building Orbitport. ~ @rezabfil, CTO & Co-Founder of @SpaceComputerIO

We built Orbitport so developers don't have to become satellite communications experts to use space services. 5 reasons why choose Orbitport to access space infra: 1/ Dev-friendly APIs A common, standardized API across satellite networks and providers. Standard REST, OAuth2, a TypeScript SDK. 2/ We handle the orbital logistics Scheduling, data packet batching, secure channels, and routing across S-Band ground stations and LEO networks like Iridium. 3/ One gateway for every service cTRNG and Key Management Service is available now, with satellite-based TEEs in production. The architecture is designed to extend to third-party infrastructure over time. 4/ No single ground station or satellite dependency Pre-allocated ground station windows, redundant bandwidth, intelligent payload aggregation, automated failover. 5/ Verifiable cryptographic security Every packet carries cryptographic (aka secure) proof, and offers satellite to consumer authentication. 🛰️ We're building Orbitport with a small group of teams that need secure, reliable access to satellites and space-based services. 👇

.@am_ylm presenting Orbitport: our secure gateway and developer friendly API for building with space infrastructure at EthPrague today 📡

Ahoj! The team has touched down in Prague 👋🇨🇿 📍The electric church of time and space

We're at @EthPrague this week! 🇨🇿 Here's where to find @semicondurian, @rezabfil, @am_ylm, and @zkpedro from the SpaceComputer team A full rundown of our talks, the hardware hackathon, and a spikey side event 👇

We just published Space Fabric. It's our secure compute verification architecture for satellites in low earth orbit, and it's the first infrastructure of its kind. Let’s see if you can explain it 👇

Understand Space Fabric, our secure orbital computing architecture in 3 minutes with @rezabfil 🚀

Introducing Proof of ET 👽 Remote attestation proves what code ran. Proof of Execution Triangulation proves where the code ran. Why this matters for space compute: → AI companies sharing orbital compute get proof their models ran on the contracted satellite, not on the ground → Governments processing classified imagery in orbit get cryptographic verification, not contractual assurance → Climate and weather data processed in space becomes independently verifiable from sensor to output How we do it: ground stations distributed across the globe independently verify that your workload executed on a specific satellite in orbit. Follow along as we build the secure space infrastructure for the space economy. 🛰️