The web as a sovereign platform.

We research, build and deploy local-first technology for public institutions and regulated environments.

Local computing·Distributed systems·Local AI
Barcelona · Europe
What we do

Research that becomes infrastructure.

Jupiter Innovation Lab works between applied research and production software. We investigate new ways of building applications around a simple principle: computation and data should remain as close as possible to the organizations and people that own them.

We turn that research into experiments, prototypes, products and operational systems — developed in real environments, from software for Barcelona City Council to publicly funded R&D and new local-first architectures for public administration, regulated environments and potential dual-use applications.

Research→Experiment→Prototype→Deployment→Product
Work

Different projects, same architecture.

Sovereign
application runtime

k3pler

Applications that carry their data and computational environment with them.

k3pler is a local-first application architecture for data-intensive, highly regulated environments. Data, business logic, analytics, GIS and selected AI capabilities execute directly on the user's device. Applications stay operational without permanent connectivity and synchronize securely when a network is available.

Public administration · Critical infrastructure · Dual-use potentialExplore k3pler →
Public technology
Production

Jupiter Pla Endreça

Software built for the complexity of a real city.

We develop operational software for Barcelona City Council, supporting the management and analysis of urban interventions and public-space operations. The work is a real environment in which to develop, deploy and validate the technologies behind Jupiter.

700+
Active users
4,000+
Interventions
Procedural media
Applied research

Toflr

Don't generate the frames. Generate what creates them.

Toflr investigates a different approach to generative media. Instead of asking a model to produce every frame, it uses AI to create structured procedural representations that can be validated, modified and rendered locally — making animation reproducible, programmable and independent from continuous cloud rendering.

The project has received public support from the Generalitat de Catalunya for its development.

AI · Procedural generation · Local renderingExplore Toflr →
Research

We build to investigate.

Our research focuses on architectures that reduce the dependency between computation and centralized infrastructure.

R01 — Local-first architectures
How much of an application actually needs a server?

We explore systems where the primary working state lives with the user and the network becomes a synchronization mechanism rather than a permanent requirement.

SQLite · OPFS · WASM · snapshots · deltas
R02 — Portable applications
Can an application become a file?

Data, interface, logic, permissions and analytical capabilities can travel together as a portable computational object. We explore this model through k3pler and its portable application architecture.

portable object · single artifact
R03 — Local AI
What happens when inference moves to the data?

Models are becoming small and efficient enough to execute on consumer and institutional hardware. We investigate AI that operates directly on local information, without that information leaving the device.

MLX · ONNX · WASM · WebGPU
R04 — Distributed synchronization
Can devices coordinate without permanent central infrastructure?

Local-first changes the role of the network. We experiment with peer-to-peer transport, encrypted replication and distributed synchronization for applications that must remain operational independently.

iroh · P2P transport · encrypted replicas
R05 — Sovereign identity
Who controls identity when the cloud is optional?

We explore authentication based on open standards, passkeys and infrastructure that organizations can operate and control themselves.

passkeys · open standards · self-hosted
R06 — Procedural media
What if generative AI produced systems instead of pixels?

Toflr explores generative models as creators of executable procedural representations rather than final media.

The model generates the system. The device generates the result.

procedural · executable · reproducible
Sovereignty

Data sovereignty is not only about where the server is.

Moving data to a European cloud can address important jurisdictional and regulatory concerns. But the location of the server does not fundamentally change the architecture of the application.

Jupiter investigates another layer of technological sovereignty: giving organizations control over where their data lives, where computation happens, how intelligence is executed and when a network is required.

Data+Compute+Identity+AI+Software

A sovereign cloud is useful.

Choosing where a server sits solves part of the problem. Jurisdiction matters. It is a necessary step — but not the whole architecture.

A sovereign computer is better.

Our goal is not to eliminate networks or cloud infrastructure. It is to make applications less dependent on them.

Local first. Network second.
Dual-use technology

Local-first by necessity.

Some operational environments cannot assume permanent connectivity, unlimited bandwidth or continuous access to external cloud infrastructure. The properties that make local-first systems useful for public administration can therefore matter to critical infrastructure and defence.

Offline operation

Applications and data remain available when connectivity is degraded or unavailable.

Controlled distribution

Information can be distributed according to roles, permissions and operational requirements.

Local computation

Queries, analytics, cartography and selected AI workloads run directly on sensitive data, without external cloud processing.

Secure synchronization

Distributed replicas synchronize when connectivity returns, while maintaining access control, integrity and encryption.

Potential applications include asset management, maintenance, logistics, technical documentation, offline cartography, field operations and local analysis of sensitive information. Deployment in defence environments would require additional integration, cryptographic hardening, classification policies, auditing, interoperability testing and the corresponding accreditation or certification.

local execution · encrypted replicas · secure synchronization · controlled access
Europe

Built in Europe. Built to remain operable in Europe.

Technological sovereignty requires more than choosing where a server is located. We favour open standards, portable data, European infrastructure where infrastructure is required, and local execution wherever it makes sense.

Our aim is to build systems that institutions can operate, understand and evolve — without unnecessary dependency on a single technology provider or hyperscaler.

Barcelona · European Union
Open

Some things are more useful when everyone can use them.

We release selected tools, experiments and design resources developed inside Jupiter.

K3pler Sans

Aa Gg 0Variable 100–900 · Open Font License

An open typeface derived from Geist and developed for the interfaces we build.

Open Font License · Download →

Halftone Studio

•••Local-first · WebGPU

A halftone studio that runs entirely in the browser. Load an image, work the grid, export SVG or an animated snippet. No image ever leaves the device.

Open the app →

Libraries

Components and tools extracted from our research and products — the reusable pieces of the local-first stack.

Notes

Technical notes from ongoing work on local-first software, distributed systems, local AI and procedural computing.

Read →
The Lab

Jupiter Innovation Lab

An independent applied technology lab based in Barcelona, working at the intersection of public technology, local-first software, distributed computing and artificial intelligence. Our work ranges from experimental systems to software deployed in public institutions.

We collaborate with administrations, research institutions and technology partners to turn architectural research into operational systems. We are interested in a small set of persistent questions.

01Why should every application require a permanent server?
02Why should organizational data leave the organization in order to be useful?
03Why should AI require sending information to somebody else's computer?
04How much software can become portable, local and independent?

Our products are attempts to answer those questions.

The network should extend the computer. Not replace it.

Work with the Lab See what we build
Barcelona · Europe