portfo


Part portfolio builder, part social network. Build your space, share your process, and find your next collaborator.

Access opens in waves. We'll send you an email when you're in.

Portfo Studio

From blank canvas to a published page people actually find.

portfo · studio

Edge Cache for a Read-Heavy API

Publish
Text
Edge Cache for a Read-Heavy API
Text
Cut P95 latency from 340ms to 42ms with a regional cache layer.
Code
// edge-cache.ts
async function getCached<T>(key: string, ttl: number, fetch: () => Promise<T>): Promise<T> {
  const cached = await redis.get(key);
  if (cached) return JSON.parse(cached);

  const fresh = await fetch();
  await redis.set(key, JSON.stringify(fresh), "PX", ttl);
  
}
Text
The problem
Text
Our API's read traffic outgrew what a single database region could serve, and P95 latency crept past 300ms during peak hours. Almost all of the slow requests were reads for data that barely changes minute to minute, which made this a solid candidate for caching. I added a regional edge cache in front of the read path, keyed by resource and region, with a short TTL plus explicit invalidation on writes. The hard part was avoiding stale reads during the invalidation window without dropping the hit rate back toward zero. The numbers below are from a week of production traffic after rollout, not a synthetic benchmark.
Text
Before and after
Table
MetricBeforeAfter
P50120ms18ms
P95340ms42ms
P99610ms88ms
Cache hit raten/a94%
Text
The same numbers, plotted
Code
Link
View benchmark repo

Your best work is buried in repos, drives, and camera rolls.

Put it on a page that does it justice.

From built to discovered.

  • Draft

    Start with what you built

    Every project page opens on the work itself: what it is, how it came together, why it's worth a look. The bio comes after, if at all.

  • Studio

    Build the page in Studio

    Arrange text, images, video, code, even a 3D model, on one canvas. The layout follows the project and nothing fights you for space.

  • Discover

    Publish it where people are looking

    Push it to Discover and it's in front of people actively browsing for work like yours, not sitting alone on a URL only you visit.

the-usual-profile.com
credentials first

Alex D. · 3rd

Results-driven electrical engineer | 10+ yrs in power & embedded systems | Passionate about circuits & innovation

500+ connections

ConnectMessage
bullet points ≠ proof

Experience

• Led cross-functional initiatives to drive impact

• Leveraged best practices across key verticals

Skills

Circuit DesignPCB LayoutEmbedded Systems
the actual work

portfolio_final_v2.pdf · updated 2019

Traditional résumés tell you the work. We show it.

Years of experience. Job titles. Metrics picked to sound impressive. All of it stands in for what you actually built, and the project itself disappears behind the numbers.

Everyone tells you what they built. Almost no one shows you.

Every kind of work. Built to be seen.

Not screenshots of your work: the work itself. Code that reads like code, charts that move, 3D you can spin. And the block library keeps growing.

Runnable code

A real, live snippet on the page, not a screenshot of one. Syntax and all.

// every kind of block, one canvas
›

3D models

Upload an STL and it renders live on your page.

Live charts

Benchmarks that actually chart.

Collections

Curate published projects into groups.

Images

Photos, screenshots, renders.

Text

Titles, captions, full write-ups.

Video

Paste a link or upload the file.

Table

Specs, benchmarks, comparisons.

Link

Demo, repo, paper, anywhere.

And more

However your work is meant to be seen, that's how it goes on the page.

One project, end to end.

The same demo project at every stage: built in Studio, opened by a visitor, and surfaced in the feed.

What you design is what they see.

No re-flowing, no watering down. The layout, the media, the write-up: it all ships exactly as you built it in Studio.

Public view

portfo · public view

Public view

Edge Cache for a Read-Heavy API

Edge Cache for a Read-Heavy API
Cut P95 latency from 340ms to 42ms with a regional cache layer.
The problem
Our API's read traffic outgrew what a single database region could serve, and P95 latency crept past 300ms during peak hours. Almost all of the slow requests were reads for data that barely changes minute to minute, which made this a solid candidate for caching. I added a regional edge cache in front of the read path, keyed by resource and region, with a short TTL plus explicit invalidation on writes. The hard part was avoiding stale reads during the invalidation window without dropping the hit rate back toward zero. The numbers below are from a week of production traffic after rollout, not a synthetic benchmark.
Before and after
MetricBeforeAfter
P50120ms18ms
P95340ms42ms
P99610ms88ms
Cache hit raten/a94%
The same numbers, plotted
View benchmark repo

made with portfo · @alexr

Discover

Projects other builders just shipped, ranked by the work itself, not follower counts.

portfo · discover

Trending

Projects gaining traction right now.

Maya Chen

Maya Chen

@mayac · 2h ago

3D-printed prosthetic hand, driven by an STM32

Printed fingers, tendon servos, STM32 firmware. Full build log inside.

3D-printed prosthetic hand, driven by an STM32
Lars Bakker

Lars Bakker

@larsb · 5h ago

Amsterdam canal house: architectural design

Elevations, sections, and floor plans for a six-dwelling infill.

Amsterdam canal house: architectural design
Tyler Brooks

Tyler Brooks

@tylerb · 6h ago

Realtime physics playground

Open in the browser, no install.

interactive demo

Get in front of people already looking.

People browse, save, and follow based on projects, not job titles. Open a post and you land on the full page, never a locked preview.

Frequently asked questions

A project-first portfolio and discovery platform. You build project pages in Studio, then publish them so people find you through the work, not a resume PDF.

Most portfolio sites only want the finished, polished result. Portfo works at any stage: post a build log, an early prototype, or the final version, and keep posting updates as the project moves forward. Discover surfaces the work itself, not follower counts.

Founders, researchers, students, writers, designers, and makers. The common thread isn't a job title, it's real work worth showing.

You can join and build your portfolio for free. The starter tier allows you to document your work, publish full project case studies, and increase your discoverability at no cost. We are actively developing advanced features that will be available in future paid tiers.

No. Keep drafts in Studio for as long as you want. Publish a project only when it's ready to be seen.

Portfo is in private beta, with access opening in waves.

Yes. Access opens in waves. Leave your email and you'll get one message when your spot is ready.

Your next project deserves a real page.

Get on the waitlist, shape your project in Studio, and share it whenever it's ready, from first prototype to finished piece.

Private beta. Access opens in waves; we'll email you when you're in.

Runnable code3D you can orbitBuild logsEarly prototypesFull write-upsLive chartsReal layoutsPost at any stageProcess includedThe messy middle