Project files
It works out the language and framework, whether it is a monorepo, and which folder is which part.
package.jsonpnpm-workspace.yamlgo.modCargo.tomlrequirements.txtGemfilecomposer.json
Feature · Project detection
It knows your project.
Point Kule at a GitHub repo or a folder on your computer. Without cloning it or running anything, Kule reads a few of its files, works out what it is and builds the deploy plan.
What it reads
A few files, a full plan.
Every finding comes with the file and the dependency that revealed it. The plan shows why it looks the way it does.
How it runs
If there is a Dockerfile, it uses it. If not, it finds the build and start commands. It also recognizes static sites.
DockerfileEXPOSEscriptsnixpacks
What it connects to
From example .env files and client libraries, it works out which database, which cache and which services it connects to.
.env.exampleprismapgioredisbullmq
What it recognizes
Most projects, at first sight.
When it finds something it does not know, it does not guess. It tells you plainly what it could not find.
Node.js
Python
Ruby · PHP
Go · Rust
Static sites
Resources
What it wires up for you
You do not write the variables.
Kule fills in the addresses and connection strings between the parts. It only asks you for the keys of outside services.
We'll let you know when Kule is out.
People on the list get the first version before anyone else.
You're on the list. You'll be the first to hear when Kule is out.
Other features