The platform provides a self-hosted backend API, scheduled work, a web dashboard, and cloud deployment definitions. It uses the published shared Go libraries for provider operations, pinned to fixed versions in go.mod.
The dashboard and provider integrations are experimental. Building the components does not provision infrastructure, create a database, or start the application.
Use the Go version declared in go.mod. The shared Go modules are published and pinned in go.mod, so this checkout builds on its own.
make build-server
./bin/cudly-server --helpmake build-server creates bin/cudly-server from ./cmd/server. The target builds the server only. It does not deploy or start it.
To build the Lambda entry point for a deployment workflow:
make build-lambdamake build-lambda creates the bootstrap artifact from ./cmd/lambda. Follow deployment guidance before using it.
The dashboard lives under frontend. Its package scripts and dependencies are defined in frontend/package.json. Use the development guide for local frontend work.
The dashboard is experimental. It shows recommendations, purchase plans, execution history, inventory, coverage, and account settings. Review provider and purchase state before enabling an operation.
Per-account service overrides are available from Settings -> Accounts. Expand an account, open Service overrides, select a provider and service, set term, payment, coverage, or enabled, and save. Blank fields inherit the global purchasing defaults. The same settings are available through PUT /api/accounts/{id}/service-overrides/{provider}/{service}.
cmd/servercontains the HTTP server entry point.cmd/lambdacontains the Lambda entry point.internalcontains platform services and API code.frontendcontains the web dashboard.terraform,cloudformation,arm, and related infrastructure directories contain deployment definitions.
This component does not provide the cudly CLI. Use the CLI component for command-line workflows.
- Amazon RDS and ElastiCache are the tested AWS service paths.
- Other AWS service paths, Azure, and GCP support remains experimental.
- Azure and GCP support is experimental and can vary by service and account.
- Deployment definitions can create billable cloud resources. Review the target, credentials, and plan before applying them.
Read deployment and development documentation before changing infrastructure or application behavior.
- CLI provides command-line workflows.
- Shared Go libraries provide provider and common packages.
- MCP server provides a separate tool interface.
CUDly is maintained by LeanerCloud and licensed under the Open Software License 3.0. See the repository license and attribution files for third-party notices.