A resume is a claim. It says you built a thing, used a stack, shipped a feature. But a recruiter scanning a stack of applications can't run your PDF. A professor grading a project can't click your bullet points. A hiring manager who wants to see if you can actually ship is left taking your word for it — or worse, opening a repo full of files they have no time to read.
The work you've already done deserves better than a description of itself. It deserves to be running, reachable, and one tap away from anyone you want to impress.
A screenshot proves you can take a screenshot
Think about what a static artifact actually demonstrates. A PDF proves you can write bullet points. A screenshot proves the app rendered once, on your machine, on a good day. A GitHub link proves the code exists — but it asks the reader to imagine the running result, install your dependencies, and trust that npm run dev works on the first try. It rarely does, and nobody clicking through applications is going to find out.
None of that is proof you can ship. Shipping means the thing builds, deploys, stays up, and survives contact with a real URL. That's the exact gap between "I built a dashboard" and "here, click it." Recruiters and professors are pattern-matching for signal under time pressure. A live link is the highest-signal thing you can hand them, because it collapses every "does it actually work?" question into a single click that answers itself.
Anyone can list a project. Far fewer can hand you a working link. Be the second kind.
The good news: you've probably already done the hard part. The coursework project, the hackathon build, the weekend side app — the code is written. What's missing isn't more work. It's deployment, a stable address, and a page that frames the work the way a reviewer needs to see it.
From repo to running proof, in three steps
Hostlet Cloud is built around one job: turn a GitHub repository into a live demo and an auto-generated portfolio page. The flow is deliberately short.
- Connect a repo. Point Hostlet at a GitHub project and it inspects the app's shape. Hostlet Cloud uses generated build support for
package.json, Python, Go, Rust, static sites, and other modern manifests. If your project needs a custom build or start command, you can override it. - Launch the demo. Hostlet builds, deploys, and keeps it reachable at a
*.hostlet.cloudURL. Every git push redeploys it, so the live version tracks your latest commit instead of rotting at whatever state you last screenshotted. - Share proof. You get a per-project showcase page with the live demo, the source context, the detected stack, and a summary — plus a public portfolio at
[you].hostlet.cloudthat collects your projects into one link. There's a mobile share-sheet for dropping it into an application, a DM, or a chat with a professor.
The result is the difference between "see my GitHub" and "see it running." One is homework for the reader. The other is the answer.
The honest part: free portfolio, paid live demo
Here's the model, stated plainly, because it changes how you should use the product.
Your portfolio and your public showcase pages are free for everyone. The generated profile, the per-project pages, the GitHub metadata enrichment, the screenshots, the one shareable link — none of that costs anything. Portfolio proof is unbounded.
What you pay for is always-on live demos — the actually-running, deployed URLs that cost real compute to keep reachable. That's the metered part, and the pricing is fixed and simple:
- Student — $4/mo — 1 live demo.
- Starter — $9/mo — 2 live demos.
- Pro — $19/mo — 4 live demos.
The right tier maps to what you're doing, not to some abstract "scale." A single course project or hackathon submission? One live demo. Applying to internships and want your two strongest builds clickable on the application? Two. Heading into portfolio season and want a handful of running apps behind your profile link? Step up from there.
This matters because it tells you where to spend. You don't need every project running 24/7. You need your best one or two live — the ones you'll actually link in an application — while the rest live on your free portfolio with their source, stack, and screenshots. Spend compute where someone is going to click.
Why a live link beats a better-formatted PDF
You could spend another evening tweaking your resume's margins. Or you could take the project you already built and turn it into something a recruiter can open, a professor can grade, and a hiring manager can poke at — running the real code, on a real URL, redeploying every time you push.
A static resume describes your work. A live demo is your work, deployed. When the question is "can this person actually ship software," nothing closes that question faster than handing someone the running answer.
Real apps. Really deployed. Every app gets its own URL.
Quick questions, quick answers
[you].hostlet.cloud portfolio, or a single project's showcase page — with a working demo behind it.Stop describing your work. Start deploying the proof.