Bookuvai
Freemium
Non-technical users describing apps in plain English
Building a government open data portal usually means months of custom frontend work on top of CKAN, or accepting a rigid CMS that fights your design system the moment a stakeholder wants a map next to a chart. PortalJS exists to collapse that gap.
$99/mo · Free tier: Self-hosted and self-managed, MIT licensed, AI skills included, community support, free deployment tier · Checked Oct 22, 2026
PortalJS is an open-source, AI-native framework where you describe the portal you want — audience, datasets, layout — and a set of documented skills scaffold a real Next.js project: pages, tables, charts, and maps wired to your data. The output is plain, editable code, not a locked runtime, so your team owns every file from day one. It decouples from whatever catalog or metadata backend you already run — CKAN, DKAN, DataHub, OpenMetadata — without forcing a rewrite. Large files stream via Cloudflare R2, and in-browser SQL queries run against Parquet via DuckDB-Wasm with no backend server required. The wall appears when your portal requires conditional data logic or workflow complexity beyond what a composable skill covers; that is when teams layer in custom Next.js code themselves.
Bottom line: Pick PortalJS when you are shipping a city or research open-data portal on an existing CKAN backend and want a fast static frontend without writing boilerplate — but plan for custom development work the moment your dataset views need logic the built-in skills do not express.
Effortless and reliable
Scalable and collaborative
Compliance-ready
Tailored for impact
Pricing may have changed since last verified. Check the official site for current plans.
Build it your way
Effortless and reliable
Scalable and collaborative
Compliance-ready
Tailored for impact
View full pricing on portaljs.com →
Pricing may have changed since last verified. Check the official site for current plans.
Find your fit
More options in Low-Code / No-Code Builders. Compare pricing, platforms, and features side by side.
Freemium
Non-technical users describing apps in plain English
Paid
Freelancers
PortalJS is an open-source framework from Datopian for building public-facing open data portals. The core workflow is three steps: describe the portal you want in plain language, let an AI assistant run documented skills that scaffold a Next.js project, then deploy a static site or connect a live backend. Skills are named, versioned, and composable — portaljs-new-portal, portaljs-add-dataset, portaljs-add-chart, portaljs-add-map, and portaljs-deploy ship out of the box, and the vendor documents how to author your own so the assistant picks them up. Both a terminal interface and a visual builder at studio.portaljs.com produce identical, editable output.
The differentiating architecture is the decoupled frontend. PortalJS does not replace your data catalog — it points at whichever backend you already run: CKAN, DKAN, OpenMetadata, Microsoft Purview, DataHub, GitHub, Frictionless, or a custom API. Swapping backends requires no frontend rewrite. For large datasets, the framework converts files to Parquet and queries them in-browser with DuckDB-Wasm, fetching only the bytes a query needs — no dedicated query server. Git LFS and Cloudflare R2 handle versioning and streaming for multi-gigabyte files.
PortalJS fits teams in government, research, and nonprofits that already operate a metadata catalog and need a fast, maintainable frontend without building one from scratch. Production examples the vendor cites include the City of Malmö, City of Ann Arbor, Transport Data Commons, and Open Data Nepal. The skills model works well for portals that follow the scaffold-once-then-extend pattern. It breaks down when a portal needs complex conditional display logic or domain-specific data transformations not covered by the built-in skill set — at that point teams are writing custom Next.js components, which is standard frontend development rather than anything PortalJS accelerates.
Hosting is self-managed or via PortalJS Arc, a Datopian-managed option that deploys static exports to Cloudflare infrastructure under a slug URL. The project is MIT-licensed, carries no runtime lock-in, and community support runs through an open Discord and public GitHub discussions. No API is exposed for programmatic platform control outside the skill and CLI interface.
Sign in to rate this tool or suggest an edit.