Deploy Floci UI

Deploy and Host Floci UI on Railway

Floci UI is a visual multi-cloud console for browsing, inspecting, and managing resources across Floci cloud emulators.

It provides a web interface for Floci AWS, Azure, and GCP environments, making it easier to explore emulated cloud resources without relying entirely on CLI commands, SDK calls, or raw APIs.

About Hosting Floci UI

This template deploys Floci UI on Railway using the official floci/floci-ui:latest Docker image.

Floci UI runs as a standalone web application on port 4500 and connects to existing Floci emulator deployments through their configured endpoints.

The UI does not include or automatically deploy AWS, Azure, or GCP emulators. At least one supported Floci emulator should already be running and reachable from this service.

Floci UI does not require persistent storage because cloud resources and emulator state remain stored in the connected Floci emulator services.

Common Use Cases

• Browse Floci AWS resources through a visual interface
• Inspect Azure resources running inside Floci Azure
• Explore GCP resources running inside Floci GCP
• Manage emulated cloud resources without relying entirely on CLI tools
• Provide developers with a shared web console for Floci environments
• Debug integration tests and cloud-emulated workloads
• Inspect data created by SDKs, APIs, Terraform, or automation workflows

Dependencies for Floci UI Hosting

• Official floci/floci-ui:latest Docker image

• Railway public networking on port 4500

• At least one reachable Floci emulator:

  • Floci AWS
  • Floci Azure
  • Floci GCP

No Railway volume is required.

Railway Configuration

Recommended environment configuration:

PORT="4500" # Railway HTTP target port

FLOCI_ENDPOINT="" # Required Floci AWS emulator endpoint
FLOCI_AZURE_ENDPOINT="" # Optional Floci Azure emulator endpoint
FLOCI_GCP_ENDPOINT="" # Optional Floci GCP emulator endpoint

AWS_REGION="us-east-1" # Default AWS region
AWS_ACCESS_KEY_ID="test" # Dummy AWS access key for Floci emulator
AWS_SECRET_ACCESS_KEY="test" # Dummy AWS secret key for Floci emulator

FLOCI_GCP_PROJECT="floci-local" # Default GCP project ID

FLOCI_AZURE_ACCOUNT_NAME="devstoreaccount1" # Default Azure Storage account
FLOCI_AZURE_RESOURCE_GROUP="floci-local" # Default Azure resource group
FLOCI_AZURE_SUBSCRIPTION_ID="00000000-0000-0000-0000-000000000000" # Default Azure subscription

No custom start command is required.

No persistent volume is required.

How to Use Floci UI

After deployment, Railway provides a public URL similar to:

https://your-floci-ui.up.railway.app

Open this URL in your browser to access the Floci visual console.

Before using the dashboard, configure at least one Floci emulator endpoint.

Connect Floci AWS

If you already deployed Floci AWS, set:

FLOCI_ENDPOINT="https://your-floci-aws.up.railway.app"

The AWS credentials used by Floci UI can remain dummy values:

AWS_REGION="us-east-1"
AWS_ACCESS_KEY_ID="test"
AWS_SECRET_ACCESS_KEY="test"

Floci is an emulator, so real AWS credentials are not required.

After redeploying Floci UI, AWS resources from the configured emulator can be browsed through the console.

Connect Floci Azure

If you already deployed Floci Azure, configure:

FLOCI_AZURE_ENDPOINT="https://your-floci-azure.up.railway.app"

The default Azure emulator configuration is:

FLOCI_AZURE_ACCOUNT_NAME="devstoreaccount1"
FLOCI_AZURE_RESOURCE_GROUP="floci-local"
FLOCI_AZURE_SUBSCRIPTION_ID="00000000-0000-0000-0000-000000000000"

These values should match the configuration used by your Floci Azure deployment.

Connect Floci GCP

If you already deployed Floci GCP, configure:

FLOCI_GCP_ENDPOINT="https://your-floci-gcp.up.railway.app"
FLOCI_GCP_PROJECT="floci-local"

The project ID should match the default project configured in the Floci GCP emulator.

Using Railway Private Networking

If Floci UI and the emulator are deployed inside the same Railway project, private networking can be used instead of public URLs.

For example:

FLOCI_ENDPOINT="http://${{floci.RAILWAY_PRIVATE_DOMAIN}}:4566"

Azure:

FLOCI_AZURE_ENDPOINT="http://${{floci-azure.RAILWAY_PRIVATE_DOMAIN}}:4577"

GCP:

FLOCI_GCP_ENDPOINT="http://${{floci-gcp.RAILWAY_PRIVATE_DOMAIN}}:4588"

Private networking keeps communication between Floci UI and the emulator inside Railway's internal network.

Public networking is still required for the Floci UI service itself if users need to access the dashboard from a browser.

Supported Cloud Providers

OCI is currently not available through Floci UI.

The OCI emulator can still be deployed and used independently through OCI CLI, SDKs, Terraform, or direct API calls.

Floci UI Architecture

A typical deployment looks like:

Browser
   │
   ▼
Floci UI
   │
   ├── Floci AWS
   │
   ├── Floci Azure
   │
   └── Floci GCP

Floci UI acts as the visual management layer.

The actual emulated cloud resources remain inside the corresponding Floci emulator.

Important Notes

• Floci UI does not include a cloud emulator.
• At least one supported Floci emulator should be configured separately.
• FLOCI_ENDPOINT connects the UI to Floci AWS.
• Azure and GCP endpoints are optional.
• Real AWS credentials are not required; dummy credentials such as test are sufficient.
• Floci UI does not require a Railway volume.
• Emulator resources and persistent state remain inside the connected emulator deployments.
• OCI is currently not supported by Floci UI.
• Use Railway private networking when the UI and emulator are deployed inside the same project.

Floci UI vs CLI-Only Workflow

Floci UI complements CLI, SDK, and API-based workflows rather than replacing them.

Why Deploy Floci UI on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

Deploying Floci UI on Railway provides a remotely accessible visual console for Floci AWS, Azure, and GCP emulators with automatic HTTPS, simple environment configuration, and optional private networking between services.