Pre-compiled native libraries, ready to deploy.
A curated catalog of pre-compiled C/C++ libraries ready for web, mobile, edge, and AI-agent workflows. Powered by Celoce Core. Free to use.
What is available today
This table separates current, documented availability from future potential. The Hub grows as new official, community, private, and enterprise packages are added.
| Category | Verified fact | Count |
|---|---|---|
| Core engine | Celoce Core is powered by cpp.js, the engine for using C++ from JavaScript across WebAssembly and React Native workflows. | 1 core engine |
| Official packages | 16 official native-library package families are already available as cpp.js packages. | 16 |
| Community packages | Community packages have started, with simdjson listed as an early community-maintained package. | 1+ |
| Integration paths | cpp.js documents 9 integration paths for existing projects across web, backend, cloud, and mobile. | 9 |
| Web integrations | Web developers can integrate through Standalone builds or bundler plugins for Webpack, Rollup, Vite, and Rspack. | 5 |
| Mobile integrations | Mobile workflows are documented for React Native and Expo. | 2 |
| Backend integration | Backend usage is documented through Node.js WebAssembly workflows. | 1 |
| Cloud integration | Cloud/edge usage is documented through Cloudflare Workers. | 1 |
| Project generator | Developers can start new cpp.js projects with npm create cpp.js@beta. |
1 generator |
| Project categories | The project generator supports Web, Mobile, Backend, Cloud, and Library project types. | 5 |
| Starter templates | cpp.js includes 12 starter templates across web apps, mobile apps, backend, cloud, and library packaging. | 12 |
| Frontend frameworks | The web starter flow supports Vanilla JavaScript, React, Vue, and Svelte. | 4 |
| AI-agent clients | cpp.js documents native AI-agent integrations for 6 clients. | 6 |
| AI-agent fallbacks | MCP and AGENTS.md provide fallback paths for broader agent compatibility. | 2 |
| Showcase examples | The cpp.js showcase includes browser geospatial and WebAssembly mobile-map examples. | 2 |
One native library, every JavaScript surface
Celoce Core does not force developers into a custom app structure. The same C/C++ library port can ship through web apps, mobile apps, backend services, edge runtimes, and reusable npm packages. Start from familiar starters or integrate into existing projects.
| Surface | Starter templates | Integration paths |
|---|---|---|
| Web | Vanilla, React + Vite, React + Rspack, Vue + Vite, Svelte + Vite | Standalone, Webpack, Rollup, Vite, Rspack |
| Mobile | React Native CLI, Expo | React Native, Expo |
| Backend | Node.js + WebAssembly | Node.js WebAssembly |
| Cloud / edge | Cloudflare Worker | Cloudflare Workers |
| Library | Prebuilt package, source package, CMake package | Prebuilt, source-based, and CMake-based packages |
We now officially distribute OpenSSL compiled to all target platforms
The OpenSSL project does not distribute pre-compiled binaries. They only publish source code. Third-party distributors fill this gap, and Celoce is now one of them. We compile and distribute the OpenSSL library to all cpp.js target platforms (WebAssembly, iOS, Android), ready to use from JavaScript with a single import.
Native libraries already represented in the Hub
Celoce Hub starts with infrastructure libraries that already matter across geospatial, database, cryptography, networking, compression, encoding, and imaging workflows.
The Hub grows when developers port new libraries
The system is designed so developers, maintainers, and enterprises can package new libraries, customize existing libraries, and publish reusable cpp.js-compatible packages.
Official packages
Maintained core packages for widely used native libraries.
Community packages
Public packages added by external maintainers and contributors.
Private packages
Internal company libraries packaged for private use.
Custom builds
Modified forks, special flags, and domain-specific builds.
Not limited to the catalog
Developers can bring their own .cpp and .h files, import C++ headers from JavaScript, generate bindings for supported APIs, and build artifacts for supported targets. This makes Celoce useful for custom algorithms, private native modules, internal company libraries, and specialized forks of existing open-source libraries.
The potential is larger than the current package count
The current Hub already shows the model: native libraries can become JavaScript-consumable infrastructure. The larger opportunity is the C/C++ software universe: decades of proven libraries that can be exposed to modern web, mobile, backend, cloud, and AI-agent workflows.
With 16 official package families and 9 documented integration paths, Celoce Hub already represents 140+ practical library × integration combinations before counting custom builds, architecture variants, debug/release modes, or private packages.
Libraries on the horizon
The same porting model can extend to other major C/C++ ecosystems. These examples show where the Hub can grow as more developers and maintainers add packages.
Use native C++ libraries
from JavaScript, everywhere.
Start locally with cpp.js. Explore official and community packages, or bring your own C++ code to web, mobile, backend, cloud, and AI-agent workflows.