Project Incubation
Small ideas for infrastructure or product, carried to a working prototype, with a named keeper and notes to match
Lychape tends operations and small experiments as a keeper tends a lamp: each system watched over, each change written in the log.
A small, practical studio for infrastructure, reliability and product experiments. The work is shown in full, the trade-offs are written down, and services are looked after once they launch.
Explore projects→A small team with a long memory, and a sharper sense of what is worth building and keeping
Lychape began as Fengteng, then became Leakei. The name has changed; the habit at the bench has not: build small tools, keep them running, learn in the open.
Hanfeng still leads the organisation, and would sooner ship a working system than polish a brand.
Corn keeps the core team in step, above all in the quiet work of maintenance and day-to-day reliability.
Contributors join through particular projects: code, documentation, operating notes, small refinements to an interface, steadier deployments.
Lychape has no wish to pass for a large agency. It is a lamplit workshop that keeps its own pace, turning out useful systems, working notes and services made to be looked after.
Small ideas for infrastructure or product, carried to a working prototype, with a named keeper and notes to match
Steadier deployment, monitoring, recovery and routine care for services already in use
What was tried, what broke, what shipped and what ought to change next, all written down
How Lychape keeps its work of use, rather than for show
Incident reports laid open, runbooks shared, and no knowledge locked in one person's head
A quiet review after every incident, so each failure becomes a page others can learn from
Monitoring, alerts and deployment pipelines set to catch a fault early, ideally before anyone using the service feels it
Infrastructure improved a step at a time, each step tested with care before the next
The tracks under way, each with its own purpose, its own phase and someone to keep it
Deployment experiments for smaller services, in pursuit of releases that repeat cleanly and roll back safely
A control-plane concept: one place to track servers, services, access notes and maintenance tasks
Monitoring and alerting experiments that prefer one clear signal to a crowded dashboard
Backup and recovery notes for services that want protection of the plain, dependable kind