Fiber AI
Build

OpenFiber

An MIT-licensed, open-source prospecting UI built on the Fiber API — run it as-is, white-label it into your product, or fork it into something new.

OpenFiber

We open-sourced our reference frontend so you never start from a blank page. OpenFiber (github.com/fiber-ai/open-fiber) is a full prospecting UI built on the Fiber API — search, enrichment, audiences, trackers, exports — that you can run in five minutes, restyle into your own brand, or gut for parts. It's MIT-licensed: use it, modify it, embed it in a commercial product, sell what you build — the only obligation is keeping the license notice.

What you get

A working UI over nearly the entire API surface — around 180 operations across 27 feature modules:

  • Search — companies (40+ filters), prospects, combined company-and-people, AI search (plain English → filters), job postings, stealth founders, blue-collar jobs, with live match counts as you type.
  • Enrichment — single lookup, batch, bulk, and live LinkedIn refresh.
  • Audiences & saved searches — list building and recurring searches.
  • Trackers — company and people signal monitoring.
  • Tools — 17 utilities from Google Maps search and depth charts to email and phone validation, plus five social-network lookups.
  • Data & account — exclusion lists, CSV import with column mapping, exports (standard CSV plus LinkedIn, Google, and Meta ads formats), and a usage/credits dashboard.

How it works

The stack is deliberately familiar: Next.js 14, TypeScript, tRPC, shadcn/ui, and the official SDK. No database, no auth provider, no third-party services — your Fiber API key is the only credential.

Calls flow browser → its own tRPC routes → Fiber SDK → api.fiber.ai. The browser never talks to Fiber directly, and the API key never reaches the client: it lives in an HttpOnly cookie (entered once on the built-in setup screen) or in the FIBER_API_KEY env var for a single-tenant deployment. That server-side proxy is what makes OpenFiber embeddable — put it behind your own login and your users never see or need a Fiber key.

Run it in five minutes

git clone https://github.com/fiber-ai/open-fiber.git
cd open-fiber/nextjs
npm install
cp .env.example .env   # set FIBER_API_KEY, or enter it on the setup screen
npm run dev            # http://localhost:3000

It's a standard Next.js app, so it deploys anywhere Node runs. With a valid key, the sidebar shows your organization and live credit balance.

Make it yours (white-label)

There's no branding config system — rebranding is editing a handful of files, all of them obvious:

WhatWhere
App name (four UI spots)src/components/layout/sidebar.tsx, src/pages/_app.tsx, src/pages/setup.tsx, src/pages/account/index.tsx
Logo / faviconnextjs/public/favicon.svg (the sidebar uses a text wordmark — swap in your logo component)
Brand colorsCSS variables (--primary, --accent, …) in src/styles/globals.css; Tailwind reads them, dark mode is pre-wired
Fontthe Google Fonts link in src/pages/_document.tsx
Which features appearthe navGroups array in sidebar.tsx — the nav is the feature registry; delete an entry and the feature is gone

A focused rebrand — name, logo, colors, trimmed nav — touches about five files. For a deeper product identity you'd own the copy and page layouts too, which is exactly what the MIT license is for.

Fork it into your own product

Every feature follows the same four-step seam, so extending the app is mechanical:

  1. a page under src/pages/<area>/,
  2. a tRPC router in src/server/routers/ wrapping the SDK operation,
  3. one line registering it in _app.ts,
  4. a nav entry in sidebar.tsx.

Search filters are Zod schemas with label maps in src/lib/schemas/, and result tables are TanStack column definitions — reshaping what users can filter on and what they see is data editing, not architecture work.

A recruiting tool

Keep prospect search, contact enrichment, and the job-change trackers; the built-in people-list module (create a list, add people, table view) is a ready-made candidate pipeline. Re-cut the prospect table columns for screening — tenure, education, skills — and hide the sales-flavored nav groups.

An internal GTM tool

Keep company and combined search, audiences, and exports — the LinkedIn, Google, and Meta ads CSV formats are already built, so territory-building → ad-audience sync works on day one. Add your own routing rules or scoring as a new router over the search results.

An AI SDR tool

Chain what's already there: AI search turns a plain-English ICP into filters, combined search finds the companies and people, batch enrichment reveals contacts, exports hand them off. Your outreach and sequencing layer plugs in where the export step ends.

What it isn't (yet)

OpenFiber is a young reference implementation, not a turnkey product: version 0.1.x, Next.js only, and deployment tooling (Docker, CI/CD) is yours to bring. Treat it as a codebase you own from day one.

Credits

OpenFiber itself is free and open source. Every call it makes bills the connected API key at normal rates — its own Account page shows usage and balance, and chargeInfo on each response stays authoritative. See Billing & credits.

On this page