// Landing page — getfossyl.dev function Landing() { const { go } = useNav(); const { authed } = useAuth(); const { toast } = useToast(); const featuresRef = useRef(null); const howRef = useRef(null); const pricingRef = useRef(null); const scrollTo = (ref) => ref.current && ref.current.scrollIntoView({ behavior: 'smooth', block: 'start' }); const ctaPrimary = () => go(authed ? 'upload' : 'signup'); const onComingSoon = (label) => toast(`${label} — coming soon`); return (
Fossyl ingests a Zope/Plone codebase — filesystem, live ZODB export, optional MySQL schema — and produces a structured archaeological report of what runs in production, what was never version-controlled, what breaks if you touch it, and what is safe to remove.
Zope/Plone systems allow code to live in two places simultaneously — the filesystem (visible, version-controlled) and the live ZODB object database (invisible, untracked, often the only copy).
A script edited through the browser five years ago by a contractor who has since left the organisation exists nowhere except the running server. If that server dies, the code is gone. If you're planning a migration, you cannot plan around what you cannot see.
Fossyl makes the invisible layer visible.{' '} It reconciles the filesystem against the live database, surfaces every script that has no version-controlled copy, and ranks each artifact by how much downstream code depends on it.
sendReferralFax last modified 2011-03-08. Still in the critical path in 2026.
{s.d}
{it.d}
Most customers buy a single scan to prepare a migration. Teams running multiple sites subscribe. Consulting firms use the Agency plan.
"We had spent four months arguing about what the old patient portal actually did. Fossyl answered the argument in 52 seconds. 693 scripts that weren't in git. We had estimated 40."
{f.a}