Get This Tool
PortalJS
Pricing
- Model
- Subscription
Summary
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.
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.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- MIT open-source license with no runtime lock-in, which means you fork, audit, and self-host without negotiating a vendor contract or discovering a proprietary dependency mid-project.
- Decoupled from your data catalog backend — CKAN, DKAN, DataHub, OpenMetadata, and custom APIs are all valid targets — so migrating your metadata system does not require rewriting your frontend.
- In-browser DuckDB-Wasm queries over Parquet files, so you can offer SQL-level exploration of multi-gigabyte datasets without provisioning or paying for a query server.
- AI skills scaffold the full Next.js project from a plain-language brief, which means a developer can have a real, editable portal codebase — pages, charts, maps — without writing repetitive boilerplate across every engagement.
- Custom skills are documented, version-controlled, and picked up automatically by the assistant, so a capability you author once is reusable across every portal your team ships.
Cons
Sign in to edit- The skills model covers a defined set of views — tables, line/bar/area/pie/scatter charts, GeoJSON maps. Portal requirements that fall outside that set — custom dataset comparison tools, conditional filtering logic, domain-specific visualizations — drop you into raw Next.js development, which PortalJS does not accelerate; teams with those requirements frequently find a general React component library and a direct backend connection is a shorter path.
- No API surface for programmatic platform control means teams that need to automate portal provisioning across dozens of datasets or departments cannot script against PortalJS itself; they script around it using the CLI or manage scaffolded repos directly, adding operational overhead at scale.
- The framework assumes a static or backend-connected deployment model. Organizations that require real-time data freshness with server-side rendering logic beyond a static export face an architecture gap — teams in that situation typically end up maintaining a custom Next.js server layer alongside PortalJS output, running two things where they expected one.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Web, Next.js
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-16T18:17:52.484Z
Best For
Who it's for
- Governments and nonprofits
- Academic institutions
- Teams already using CKAN or similar backends
What it does well
- Municipal and national open data portals
- Research data catalogs
- Transport and sector-specific data platforms
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare PortalJS
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is PortalJS free?
- PortalJS has a permanent free tier alongside paid upgrades. You can keep using a baseline version indefinitely without paying.
- Is PortalJS open source?
- Yes. PortalJS is open source.
- Can I self-host PortalJS?
- Yes. PortalJS supports self-hosting on your own infrastructure.
- What platforms does PortalJS support?
- PortalJS is available on: Web, Next.js.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
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.