What Is Rinji?
Temporary infrastructure that knows it's temporary. Spin up a server, a database, an API endpoint -- use it for hours or days, then let it vanish. No cleanup, no lingering processes, no forgotten instances bleeding money. Rinji builds things designed to disappear.
Why Temporary?
Because permanent infrastructure for temporary problems is waste. Dev environments, staging servers, demo instances, load test clusters -- they all have expiry dates. Rinji encodes the expiry date into the infrastructure itself. When the TTL hits zero, everything dissolves. Cleanly.
How It Works
One command. Specify a TTL (time-to-live). Rinji provisions the environment, hands you credentials, starts the countdown. You build, test, demo, break things. When time's up, rinji tears it all down. No manual cleanup. No orphaned resources. The infrastructure was always temporary -- rinji just makes that explicit.
The Philosophy
臨時 (rinji) is the Japanese concept of the provisional -- the arrangement made for right now, with the understanding that right now is all there is. In software, we pretend things are permanent. Rinji stops pretending. Every server it builds carries a death date in its metadata. Honesty as a service.
Getting Started
Install the CLI. Authenticate once. Then it's just commands and TTLs. No dashboards, no GUIs, no settings pages. The terminal is the interface because temporary things don't need permanent control panels.
This page is temporary. Like everything rinji.dev builds.