floci/floci-ui repository overview

⁠Floci UI

Any Cloud. Locally.
A local-first, cloud-aware runtime console for Floci and compatible local cloud emulators

Floci UI is the first-party web console for the Floci ecosystem, built around a unified Cloud Explorer and a cloud-aware Console Home.

It renders only real data returned by local runtimes, plus explicit placeholders for work that is not wired yet. No fake resources, no demo rows, no mock operational data.

⁠Quick Start

docker compose up                      # AWS only
docker compose --profile multicloud up # AWS + Azure + GCP

Open http://localhost:4500⁠.

⁠Service Coverage

The sidebar and Console Home are rendered from GET /api/clouds/:cloud/services, so coverage is derived from the service catalog and adapter registry rather than maintained by hand.

Console Home is available for all three clouds. Regenerate the matrix after any catalog or adapter change:

cd packages/api && bun run scripts/service-matrix.ts

Services marked No render as a disabled sidebar row whose tooltip carries the server-supplied reason. Adding one is a catalog row in packages/api/src/cloud-spi/serviceCatalog.ts plus an adapter, with no frontend change.

Known runtime gap: Azure Serverless has a registered adapter, but the floci-az runtime answers 501 NotImplemented for Azure Functions, so it reports coming_soon with that reason.

⁠Architecture

Browser
  -> frontend (React / Vite)
  -> /api/clouds/*
  -> Cloud Adapter Registry
  -> provider adapter
  -> local runtime

The guiding rules:

• The UI does not know clouds.
• The proxy does not know internal implementations.
• The SPI defines the contracts.
• The adapters perform the translation.
• The runtimes execute the real behavior.

⁠Local Development

Requires Node.js 20+, pnpm 9+, Bun, and at least one running Floci runtime.

pnpm install
cp .env.example packages/api/.env
pnpm dev            # frontend on 4500, API on 4501

Split commands: pnpm dev:api, pnpm dev:web. Verify with pnpm lint, pnpm type-check, pnpm test, pnpm build.

The API runs from packages/api and loads environment variables from packages/api/.env.

⁠Environment

FLOCI_ENDPOINT=http://localhost:4566
FLOCI_AZURE_ENDPOINT=http://localhost:4577
FLOCI_AZURE_ACCOUNT_NAME=devstoreaccount1
FLOCI_GCP_ENDPOINT=http://localhost:4588
FLOCI_GCP_PROJECT=floci-local
AWS_REGION=us-east-1
AWS_ACCESS_KEY_ID=test
AWS_SECRET_ACCESS_KEY=test
PORT=4501

⁠Troubleshooting

errorCode distinguishes the cases: operation_not_implemented means the runtime does not implement the service, runtime_unavailable means it cannot be reached, and operation_not_supported means no adapter is registered.

⁠Community Consoles

Floci UI is the first-party console, not the only one. floci-dash⁠ is an AWS-Console-style dashboard built on Cloudscape Design, shipping as a single Docker image with an EC2 web terminal. It targets the AWS runtime only, while Floci UI also covers Azure and GCP.

Building something for Floci? Open a PR to add it.

⁠Resources

• Source: github.com/floci-io/floci-ui⁠
• Website: floci.io⁠
• Slack: Join the Flock⁠
• Discussions: github.com/orgs/floci-io/discussions⁠
• Sponsor: github.com/sponsors/floci-io⁠

⁠License

MIT. Part of the Floci⁠ ecosystem.