Private beta — Celoce Cloud: distributed builds with remote caching

Build C++ once. Ship everywhere.

The build platform for native code. Compile, package, and ship C and C++ to WebAssembly, iOS, Android, and JavaScript from a single workflow.

The world's most valuable performance code still lives in C and C++. Celoce makes it run everywhere modern software ships, without rebuilding the toolchain every time.

Outputs: .wasm .js .a .so .xcframework
THE NATIVE DELIVERY GAP

Shipping native code to modern platforms is fragmented and expensive.

Every new platform target compounds complexity across toolchains, builds, bindings, and artifacts. The work is repeated by every team, on every project.

01

Fragmented Toolchains

Every target — WebAssembly, iOS, Android — brings its own build logic, dependency management, and packaging rules. None of them share a workflow.

02

Manual Binding Debt

Moving native code across the FFI boundary means hand-written bridges that degrade performance and rot over time.

03

No Artifact Reuse

Build environments are ephemeral. The same artifacts are recompiled from scratch instead of cached and shared across developers and CI.

04

Release Pipeline Sprawl

Every platform adds another release pipeline to maintain. What should be one build becomes a permanent operational tax across web, mobile, and backend.

And the pressure is rising. AI assistants now generate working C++ faster than teams can compile, package, and ship it across runtimes — turning delivery, not authoring, into the bottleneck.

ONE WORKFLOW

One workflow instead of many.

Native delivery today depends on disconnected tools that were never designed to work together. Celoce unifies compilation, bindings, packaging, caching, and distribution into a single path — from .cpp to every target.

Source
.cpp .h CMakeLists
Celoce
resolve compile bind cache distribute
Targets
.wasm .js .a .so .xcframework

JavaScript can now import C++ natively, everywhere.

app.js
1
2
3
4
// import C++ headers like ES modules
import { Dataset } from './gdal.h';

const ds = new Dataset('map.tif');
emits.wasm

cpp.js binds C++ APIs to JavaScript without hand-written binding code. Import C++ headers like ES modules; cpp.js plugins generate the bindings for you. C++ classes, functions, and types from C++11 and C++14 appear as native JavaScript objects. It compiles to WebAssembly for web and Node.js, and to native machine code for iOS and Android, and integrates with Webpack, Rollup, Vite, Rspack, React Native, Metro, Gradle, and CocoaPods.

In one matrix benchmark, cpp.js ran up to 6.75x faster than the equivalent JavaScript. Results vary by workload.

existing workarounds

The costly workarounds teams rely on today.

Without unified tooling, teams adopt workarounds that increase cost and limit native code reuse.

01

Rewrite in JavaScript

Teams rewrite proven native libraries simply to reach new platforms. Performance declines while maintenance costs increase.

02

Manually maintain bindings

Manual bindings create long-term maintenance overhead and rarely cover the full API surface of the underlying library.

03

Maintain large local toolchains

Developers spend significant time setting up environments before contributing code. Onboarding takes hours.

04

Duplicate build infrastructure

Every new platform introduces another build pipeline and another operational burden.

VALIDATED IN PRODUCTION

Validated on one of the world's hardest native libraries.

We did not start with "Hello World." We built Celoce by compiling GDAL — one of the most complex open-source native libraries in existence — into a browser-ready artifact, now used across 200+ open-source and production geospatial projects.

gdal3.js
GDAL compiled for browser and mobile runtimes

GDAL is a widely used geospatial library across open-source and commercial GIS workflows, including QGIS-based workflows.

Compiled through the cpp.js workflow, gdal3.js delivers 160+ raster and vector format support directly in browsers and mobile applications.

240k+
NPM Downloads
5k/wk
Weekly Installs
160+
GIS Formats
Up to 6.75x
Faster than JS
github.com/bugra9/gdal3.js ↗
THE CELOCE STACK

One platform. Every runtime.

From local development to enterprise deployment, Celoce provides a consistent path for compiling, packaging, and distributing native software.

Managed Infrastructure
Celoce Cloud
Remote builds and artifact caching

Distributed compilation and content-addressed caching cut build time and remove local toolchain setup.

  • Remote build execution
  • Distributed compilation
  • Content-addressed artifact caching
  • Pay-per-build pricing
  • CI acceleration
Self-Hosted Platform
Celoce Enterprise
Self-hosted build control plane

Private build infrastructure on your own systems. Internal binary registries, reproducible builds, and full operational control.

  • Private build infrastructure
  • Internal binary registries
  • Reproducible builds
  • RBAC and audit logging (planned)
  • SSO integration (planned)
  • Air-gapped environments
who uses celoce

Built for modern software delivery.

From developers and CI/CD systems to automated workflows, Celoce provides a consistent interface for native software distribution.

Developers

Use cpp.js locally or via Celoce Cloud. Full CLI, dashboard, and documentation-first workflows.

CI/CD and enterprise systems

Build pipelines, backend automation, and internal systems integrate via CLI and REST API.

AI-assisted development

Agents and automated workflows get programmatic access to native compilation and distribution through one consistent API.

celoce hub · free

A growing native-library network, free to use.

Celoce Hub is the library catalog powered by cpp.js. Use maintained, prebuilt C and C++ packages, or bring your own code to web, mobile, backend, edge, and AI workflows.

16
official packages
Native C/C++ libraries including GDAL, OpenSSL, SQLite, curl, and more.
12
starter templates
Web, mobile, backend, cloud, and library templates.
9
integration paths
Standalone, bundlers, Node.js, Cloudflare Workers, React Native, and Expo.
6
AI-agent clients
Claude Code, Cursor, Codex CLI, Copilot CLI, Gemini CLI, and OpenCode.
roadmap

Roadmap.

What we've shipped, what we're building now, and what's coming next.

SHIPPED 2024 - 2026
  • cpp.js v1: cross-platform build system
  • Multi-target builds: web, iOS, Android
  • gdal3.js: 240k+ downloads
  • 16 prebuilt libraries shipped: gdal, proj, spatialite, geos, sqlite3, openssl, curl, iconv, zlib, zstd, geotiff, tiff, jpegturbo, lerc, webp, expat
  • Cloud Build private beta
  • Native AI-agent integrations: Claude Code, Cursor, Codex CLI, Copilot CLI, Gemini CLI, OpenCode
NOW H2 2026
  • cpp.js v2 beta, migrated all official libraries to v2 infrastructure
  • Universal MCP server (@cpp.js/mcp) with Skills CLI fallback
  • Cloud Build public launch with Git integration and PR previews
  • Celoce Registry for sharing compiled modules
  • Team workspaces and SSO
PLANNED Q4 2026
  • Rust interoperability support
  • Additional language targets (Go, Kotlin, Swift)
  • Desktop targets: Windows, macOS, Linux
  • Native Node.js addons (N-API)
  • Self-hosted enterprise build control plane
  • SOC 2 and ISO 27001

Ship native software everywhere,
from a single workflow.

Start locally with cpp.js. Scale to managed cloud builds when you are ready.