Opportunities › Git hosting with reduced ecosystem lock-in › Proposed app
Ferrylane
Git hosting with pull requests and issues you can export or self-host any day
- Score
- 55
- confidence 56
- Evidence
- 4
- items on the page
- Rivals
- 1
- named in sources
- First version
- 90 d
- estimate
- Type
- Desktop and mobile
- PWA: on computers and phones alike
- Market since
- 2008
- Mature market · AI estimate
ScreensConcept
Desktop and mobile: Pull request reviews happen on phones while traveling, but merging, setup, and lock-in decisions require desktop dashboards and configuration screens. Sample screens on a computer and a phone, in the proposed brand. Their numbers are sample data.
Lock-in check
Last export test: today6 of 7
About this appAI proposal
Ferrylane is git hosting for teams that like the bundled workflow (pull requests, issues, CI runs) but don't want to be stuck with it. Reviews, discussions and issues are stored in plain, documented formats that travel with the repository.
Export the whole workspace at any time as one archive, mirror it to another host, or run the same Ferrylane server on your own machine. Moving in is a guided import. Moving out is one button.
It is built for development teams and organizations that want control over their tools. Review and triage screens work on a phone, so a pull request does not wait for a laptop.
- Tagline
- Your code, your workflow, your exit.
- Voice
- PlainCandidSteady
- Why this name
- A ferry lane is a regular crossing between two shores. It suggests moving between hosts freely, in a plain, pronounceable name.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Pull requests stored with the repo
Reviews, comments and approvals are saved as open-format files that sync alongside your branches, so they leave with a clone.
No member yet
One-button full export
Download repos, issues, pull requests, labels and members as one documented archive that another host can import.
No member yet
Self-host with the same app
Run the identical server on your own infrastructure. Hosted and self-hosted workspaces can mirror each other.
No member yet
Issue tracking with plain exports
Boards and issues export to Markdown and JSON and can be imported from other hosts, so triage history is never trapped.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F6F6BHarbor Teal · primary#F6F3ECChalk · surface#1F2A2EDeep Slate · text#D9822BBuoy Orange · accent#3B5B92Tide Blue · data
Typography
Aa
Ferrylane
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Your code, your workflow, your exit.
PricingAI proposal
GitHub's verified pricing page lists a free plan and two paid plans from $4 to $21 by usage. Team and Organization tiers sit inside that range as a starting point to test, not a proven price.
Free
Free
- Public and private repos
- Pull requests and issues
- Full export and self-host
Team
$4 a month
- Per user
- Hosted CI minutes included
- Continuous mirror
- Lock-in check reports
Organization
$16 a month
- Per user
- Single sign-on
- Audit log
- Priority support
- Self-host license
Would you pay Team · $4 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Teams share public repos, review links and read-only project pages with outside contributors and clients. Each page shows a small 'hosted on Ferrylane, exportable' footer.
- Do they become customers?
- Outside contributors are often developers who run their own repos, so some may become paying users. Test how many visitors from shared links create a workspace within 30 days.
- First customers
- Small development teams of 5 to 25 people, led by an engineering manager or CTO, who say vendor lock-in is a concern and already pay for a hosted git platform.
- Where to reach them
- Hacker News: Post a Show HN with a working import and export demo, and answer lock-in questions in threads.
- Open-source maintainers: Offer free hosting and migration help to a few active projects that care about portability.
- Engineering manager communities: Offer a free lock-in audit of a team's current workflow and a dry-run import.
- First milestone
- Ten teams complete a dry-run import and five of them pay for a Team plan within 60 days.
Why people already pay for this
- Public claimGitHub's main value is not git itself but the bundle of tools and conveniences streamlined into a workflow that organizations depend on
- Public claimMany paying customers are trapped in the GitHub ecosystem, giving them limited ability to avoid unfavorable changes
- Public claimGitHub's lock-in allows it to extract increased value from users with limited recourse
- VerifiedGitHub's pricing page lists 2 paid plans, from $4 to $21 by usage, plus a free plan
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Git serverGit smart HTTP and SSH serviceHosting repositories needs a git server that also runs unchanged when self-hosted.
- This app · Object storageS3-compatible blob storageRepository data and export archives are too large for the database.
RisksAI inference
- CommercialThe material says the bundle is the value. A host without a team's existing network, integrations and habits may not make teams switch, even if lock-in annoys them.
- TechnicalHosting git, running CI and keeping an open review format in sync is a large build. Security and uptime expectations are high from day one.
- DataImports from other hosts may lose comments, permissions or links. A partial move would damage the lock-in promise.
- PlatformOther hosts could change their APIs or export limits, making import and mirroring harder.
- CommercialSelf-hosting and easy export make leaving simple, so retention must come from value, and paid conversion may be low.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.