DEV3 Technologies home

Launch Offer: up to 50% off

This item is 50% off: $24.50 instead of $49

Ends in
--
Days
--
Hrs
--
Min
--
Sec

DEV3 Biofern – Link-in-Bio SaaS Laravel Script with Block Editor, Scheduled Links, Tip Jar & Analytics

A multi-tenant link-in-bio SaaS on Laravel 12 and Filament 4: block editor with phone preview, scheduled links, tip jar with payouts, email capture, honest analytics, custom domains and an API. Web installer and demo data included. No mobile apps.

by DEV3 TechnologiesVerified Author(0) 0 sales 0 viewsUpdated 08 Nov 2026

Video tour. Pick a section below to browse 104 screenshots in 8 sections.

App & phone tours

Tap play to watch each app. Nothing downloads until you do.

  • Mobile web1:09

Biofern is a link-in-bio platform that you run as a multi-tenant SaaS, built by DEV3 Technologies on Laravel 12 and Filament 4. A creator signs up, claims a handle and builds a one-page site from blocks: links, headers, socials, embeds, an image grid, email capture, a tip jar, a countdown, a map, an FAQ and rich text. The page lives at yourdomain/handle or on the creator's own domain. You sell the plans.

What it does

  • A block editor with a live phone preview. Drag to reorder, edit inline, pick a theme or set your own colours, write scoped custom CSS, publish a frozen version and roll back to any of the last 20. On phones the editor becomes a bottom sheet.
  • Handles done properly. Live availability check, reserved names, a change cooldown, 301 redirects from the old handle and claims that cannot race.
  • Scheduled blocks. A link can appear at 9 am in the creator's own time zone and vanish later; pages are cached exactly until the next change.
  • Tip jar with rewards. Supporters tip through a simulated card page; creators receive a wallet balance, a held period and weekly payout batches you export as CSV. Digital rewards unlock with a signed link.
  • Email capture. Consent text is stored with every subscriber; optional double opt-in; one-click unsubscribe; CSV export.
  • Honest analytics. Views, uniques, clicks and CTR per block, with bots filtered out and breakdowns by referrer, device, country and UTM, plus the Link Garden chart.
  • Custom domains. TXT and CNAME verification, a Caddy-ready ask endpoint, neutral page when a domain stops verifying.
  • Trust and safety. Verified badges with evidence review, abuse reports, sensitive-content interstitial and page suspension.
  • SaaS plans and an operator panel. Three plans, billing, invoices, team members, a REST API with OpenAPI, and a web installer with demo data.

What you should know

  • The operator is the merchant of record for tips. Creators cannot connect their own payment account in this version; you pay them out from the weekly batch.
  • Payments, mail and DNS run on simulated drivers until you configure real ones.
  • Custom-domain TLS is terminated by your web server or proxy; the guide shows an on-demand Caddy example.
  • Visitor countries are fictional until you install a GeoLite2 file.
  • Embeds use an allow-list of provider patterns.
  • Web only, no mobile apps.

Requires PHP 8.2+ and MySQL 8 or MariaDB for a live site. Documentation, a buyer guide and six months of support are included.

#link-in-bio#bio-link#linktree-alternative-script#creator-tools#saas#multi-tenant#laravel#filament#tip-jar#php-script#landing-page

How it's built

Architecture, stack, key decisions and the quality gates DEV3 Biofern passed before release.

The engineering behind Biofern: unique-index handle claims, pages cached until the next scheduled block change, bot-filtered analytics that rebuild to the same totals, and a tip ledger with holds, refunds and payout batches.

The problem it solves

A link-in-bio product looks simple until two people claim one handle in the same second, a scheduled link must appear exactly on time on a cached page, a tip callback arrives three times, or a refund lands after the payout. Each of these has to be right without slowing the public page.

Architecture and approach

Biofern is a Laravel 12 application with two Filament 4 panels, server-rendered public pages and a JSON API. Handles are claimed under a unique index, never check-then-insert. Published versions are frozen, and the page cache key includes the next schedule boundary, so a block appears or disappears exactly when its window opens. Analytics write after the response with upserts, bots are stored but excluded, and a nightly rebuild must equal the incremental totals.

Tips settle only on the payment event, under a row lock, with duplicate and late events turned into durable refunds. Wallet balances are held for a period, refunds after a payout go negative and are netted from the next batch, and a check command reconciles every wallet against tips, refunds and payouts.

Quality gates and results

Biofern 1.0.0 passed the seven release gates on the final code: Larastan level 6 with no errors, a full Pest suite, a headless smoke over every page and eight MySQL race groups (handle claims, handle changes, repeated tip callbacks, expiry versus success, payout batches, subscribes, parallel clicks and publish versus edit), plus an installer test from the zip.

Tech stack

Area Technologies
Application Laravel 12, Filament 4, Blade, REST API
Data MySQL 8, Row locks, Unique-index claims
Quality Pest, Larastan level 6, Headless Playwright smoke

Inside the build

Hero: Hero — "One page for everything you make" with the handle claim field and a framed phone showing the Wren & Kiln page over a photo of a hand at the wheel.

Dark mode: The same home page on a deep fern night with the claim field, call to action and phone frame, remembered from the theme toggle in the header. Dark mode — The same home page on a deep fern night with the claim field, call to action and phone frame, remembered from the theme toggle in the header.

Guides & articles

Practical guides and engineering write-ups for DEV3 Biofern.

Link-in-bio page for creators: 7 things to check before you pick a tool

Last updated
Link-in-bio page for creators: 7 things to check before you pick a tool: DEV3 Biofern

A link-in-bio page is judged in the first few seconds on a phone. Here are seven things to check before you pick a tool, with DEV3 Biofern as the worked example.

Video tour — from claiming a handle to a tip and the analytics

Biofern home page: claim a handle next to a hand shaping clay

1. How fast does the page load?

The page should be plain HTML with a little inline CSS and almost no JavaScript. Biofern renders on the server, caches until the next schedule change and keeps the page under a few dozen kilobytes plus images.

A finished bio page on a phone: links, a countdown and a tip jar

2. Can you schedule links?

Drops, sales and events need a start and an end in your own time zone, enforced when the page is served rather than by a cron job.

The schedule picker on a block

3. Can people tip you, and who holds the money?

Ask who is the merchant of record, how long money is held, and what happens to a refund after payout. Biofern credits a creator wallet, holds it for a period and pays out in weekly batches.

The tip jar on a page

4. Do you own your audience?

Email capture should store the consent wording and let you export a CSV.

5. Are the numbers honest?

Bots and previews should not count as visitors. Biofern filters them and shows clicks, views and click-through per block.

The Link Garden: one bar per block, longer for a better click-through

6. Can you use your own domain?

A custom domain needs a verification step and a plan for TLS.

7. What happens with unsafe content?

Look for a sensitive-content gate, abuse reports and a verified badge process.

Limits

Creators cannot connect their own payment account in this version, so the operator pays out from a weekly batch. Payments, mail and DNS are simulated until you configure real drivers, visitor countries are fictional until you install a GeoLite2 file, and the product is web only.

Frequently asked questions

The complete source code (version 1.0.0) as a download from your account, with the setup and usage guides shown on this page. You can modify the code to suit your product.

Buying guides: Laravel scripts with Filament panels and a web installer · Next.js or Laravel for a SaaS script?

More from this author

View all

Related in Web Scripts & Software

View all