Websites and hosting decision
Cargo
A competent developer can replicate Cargo's core portfolio-site features and self-host them in about a week; Cargo's differentiated value is its curated showcase/community and hosted convenience, which are not hard moats.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Cargo alternatives, with the arithmetic →
What a replacement has to do
- Allow a user to create a simple portfolio site from templates, upload and manage images/media, arrange gallery pages and project entries, and publish the site to a custom domain with CDN-backed hosting.
What it still won’t have
- Curated community discovery / network of showcase sites hosted by Cargo
- Any proprietary templates or managed themes not replicated
- Zero-config integrated hosting and onboarding flow
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Cargo does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal portfolio site builder using Next.js (React) + Node backend, store content in SQLite (or a small PostgreSQL), and media in S3-compatible storage. Core features in scope: template-driven site rendering, authenticated admin for CRUD of projects (title, description, tags, images), image upload with server-side resizing and thumbnail generation, static export/deploy to Vercel or S3+CloudFront, custom domain + automated Let's Encrypt SSL. Out of scope: multi-tenant billing, large-scale community discovery feed, WYSIWYG page editor. Include input validation, upload error handling, basic unit tests for backend CRUD and integration test for deploy flow, and a README with deployment steps.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score90
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productCargo - official product
- open sourcedecaporg/decap-cms
- open sourcewebstudio-is/webstudio
Integrity checks
What held up, and what did not.
