Providers
Cloud, source control, DNS, and future storage connections
Overview
From provider connection to production operation
ForgedBase platform overview
ForgedBase is a hosting operations workspace for connecting providers, provisioning servers, launching sites, managing deployments, routing domains, issuing SSL certificates, and keeping the whole workflow visible for your team.
Runtimes
Laravel, MyBB, PHP, HTML, Nginx, PHP-FPM, databases, Redis, Supervisor
Operations
Deployments, SSL, domains, backups, commands, queues, schedulers, SFTP
Workspace
Teams, billing, limits, permissions, activity, notifications, realtime progress
Start here
Quick start
A typical ForgedBase launch moves through four practical stages. Each stage keeps enough detail visible to understand what happened, what is happening now, and what you can safely do next.
1
Connect a provider
Connect DigitalOcean for servers and a source control provider for repository-backed sites. Provider metadata must be synced before it can drive provisioning choices.
2
Provision a server
Choose the project, region, image, size, SSH key, runtime services, and database options. ForgedBase then tracks the initial provisioning run from queue to ready state.
3
Create a site
Pick Laravel, MyBB, plain PHP, or static HTML, attach a repository or blueprint, choose runtime settings, and configure the domain strategy before the site run starts.
4
Deploy and operate
Use push-to-deploy, deployment history, logs, commands, scheduled jobs, queue workers, notifications, SSL, and activity feeds to keep the site understandable after launch.
Workflow
Core workflow
The platform is built around a calm sequence: connect accounts, prepare infrastructure, launch an application, then operate it from resource-specific pages instead of scattered scripts and notes.
Provider readiness
Sync projects, regions, sizes, images, SSH keys, repositories, branches, and provider account details before using them in launch forms.
Provisioning visibility
Follow server, site, database, SSL, DNS, and maintenance jobs through status pills, history rows, and activity records.
Launch management
Manage deployments, environment settings, document roots, PHP versions, domain routing, certificates, and release state from the site workspace.
Connections
Providers
Providers give ForgedBase the accounts and metadata it needs to create infrastructure and deploy from source control. A connected provider is not considered ready until its metadata has completed a successful sync.
DigitalOcean infrastructure
Create and inspect droplets, projects, regions, sizes, images, SSH keys, provider account details, and DNS zones used for automatic domain records.
GitHub source control
Connect repositories, branches, deploy keys, deployment webhooks, blueprint forks, and push-to-deploy flows for site releases.
GitLab source control
Connect GitLab accounts for project, branch, tag, deploy key, webhook, and repository archive workflows where enabled.
Coming provider slots
AWS, Akamai, Vultr, Hetzner, storage providers, and other catalog entries can be surfaced as availability grows without changing the workspace model.
Operational notes
Sync actions are locked while a provider run is active, so duplicate refreshes and disconnects do not collide.
Advanced provider details expose account metadata, synced resource counts, last sync time, and raw failure messages.
Server creation depends on synced infrastructure metadata; site creation depends on source control access and repository metadata.
Infrastructure
Servers
Servers are the runtime home for sites, databases, scheduled jobs, queue workers, SFTP users, SSH keys, and maintenance actions. The server workspace separates initial provisioning from later operational tasks.
Guided creation
Choose a provider project, region, image, size, SSH key, hostname, PHP version, database engine, Redis, Supervisor, firewall defaults, and runtime packages.
Provisioning history
Track queued, running, failed, retried, and completed provisioning runs with step markers, activity records, and failure context.
PHP management
Install additional PHP versions, set CLI and site defaults, edit managed PHP-FPM or CLI configuration, and refresh runtime status.
Maintenance actions
Queue service restarts, server reboots, provider refreshes, package refreshes, and other background server operations from the dashboard.
Operational notes
The main server provisioning screen describes the initial create-server lifecycle; later installs have their own progress surfaces.
Nginx is the default web server for app-server provisioning, with PHP, database services, Redis, Supervisor, and firewall rules layered in as selected.
Server commands and activity feeds give you the audit trail when a background action needs deeper inspection.
Applications
Sites
Sites combine an application preset, server, source control settings, runtime settings, domain behavior, SSL, deployment configuration, environment variables, and operational tools into one launch workspace.
Application presets
Start from Laravel, MyBB, plain PHP, or static HTML. Presets shape document root defaults, source control behavior, database needs, and blueprint options.
Repository setup
Attach a custom repository, branch, tag, deploy key, and composer install behavior, or prepare supported blueprint repositories where available.
Runtime settings
Control document root, PHP version, database attachment, environment variables, config cache behavior, queue restarts, and site avatar metadata.
Site settings
Update general settings, source control, deployment settings, notification routing, domains, runtime choices, and destructive lifecycle actions from scoped panels.
Operational notes
Every site can have a ForgedBase platform subdomain for immediate access while custom DNS and SSL are being configured.
Site provisioning records the first install; deployment history records release attempts after the site exists.
Destructive site and server actions use confirmation flows so accidental removal is harder.
Release flow
Deployments
Deployments move repository code into a site release while preserving history, logs, selected run details, webhook state, and release activation context.
Push to deploy
Enable repository webhooks so commits can trigger deploy runs automatically when the connected provider supports it.
Manual deploys
Run a deploy from the site workspace using the current deployment settings, selected source reference, and configured deploy script.
Deploy scripts
Maintain the commands used for releases, including dependency installation, framework cache work, migrations, or project-specific tasks.
History and retention
Review deploy status, timing, logs, selected run details, and retention settings so old runs do not crowd the workspace forever.
Operational notes
Deploy key and webhook management live with the connected source control provider and the site deployment settings.
Notifications can be configured per site for deployment success and failure events.
If deployment state needs a reset, ForgedBase keeps that action scoped to deployment state rather than rewriting the whole site record.
Network
Domains and SSL
Domain tooling helps route traffic, configure provider DNS records, manage platform subdomains, redirect primary domains, and issue or renew certificates.
Custom domains
Add site domains, validate fully-qualified hostnames, track status, and configure primary domain behavior such as www redirects or wildcard handling.
Platform subdomains
Reserve an allowed subdomain under the configured ForgedBase platform domain so a site can be opened before custom DNS is complete.
DNS automation
When the connected provider can manage DNS, ForgedBase can create or remove the needed records and report whether a zone was created or reused.
Certificates
Issue, monitor, and renew SSL certificates with challenge status, certificate records, automatic renewal scheduling, and failure details.
Operational notes
Platform-domain SSL can be managed separately from custom-domain certificate work.
Domain disabled pages and DNS refresh commands exist for operational recovery when a domain is intentionally disabled.
Certificate and DNS jobs are realtime-sensitive and preserve channel, event, and payload behavior.
Storage
Databases and backups
Database tools cover server-level database engines, site database attachment, database creation, user creation, credentials, local backups, scheduled backups, and plan-aware backup access.
Database installation
Install MySQL or PostgreSQL on a server during provisioning or later from the Storage tab, with progress and failure state shown near the action.
Databases and users
Create databases, generate credentials, create scoped users, mark read-only users, view related sites, and reveal connection details when needed.
Backups
Run on-demand backups, inspect database backup records, download local backups, delete backups, and manage scheduled database backup jobs.
Plan access
Database backups are plan-aware, so paid workspace capacity unlocks backup management while the underlying database records remain visible.
Operational notes
Generated credentials are shown through scoped modals and are not mixed into unrelated panels.
Backup schedules are queued through the scheduler command that checks for due database backup schedules.
Storage providers are represented in permissions and connection surfaces for future remote-backup destinations.
Access
SSH, SFTP, and keys
Access management covers account-wide SSH keys, server-only SSH keys, provider-attached SSH keys, generated server credentials, SFTP accounts, deploy keys, and workspace permissions.
Global SSH keys
Save named public keys on your account, validate and normalize the OpenSSH key line, sync the key to existing servers, and include it on future servers.
Server-only keys
Add exception or temporary keys from an individual server page without pushing them to every server in the workspace.
SFTP access
Create SFTP users with directory scope, read/write mode, password or SSH-key authentication, optional recipient email, and editable access details.
Deploy keys
Generate and manage repository deploy keys for site deployments so servers can fetch private source code without broad account credentials.
Operational notes
SSH sync waits until a server has a public IP and the provisioning access needed to install the key.
Server activity records whether a key install was completed, skipped, already present, removed, or failed.
Provider-attached SSH keys remain managed in the cloud provider; ForgedBase displays and uses them during server creation.
Runtime
Commands, schedulers, and processes
Runtime operations help you run one-off commands, manage queue workers, configure scheduled jobs, control background processes, and keep long-running work visible.
Server commands
Run server-level commands when permitted and review command run records from the server workspace.
Site commands
Run site-scoped commands from the selected working directory and inspect command output without leaving the site.
Background processes
Create and manage Supervisor-backed processes, queue workers, command names, working directories, process counts, stop signals, and restart behavior.
Scheduled jobs
Manage scheduled command entries for recurring site tasks such as Laravel scheduler-style jobs and operational maintenance commands.
Operational notes
Process, scheduler, and command controls respect workspace permissions so viewers can inspect without operating infrastructure.
Long-running jobs surface status near the panel that started them instead of hiding progress in a separate system.
Queue worker and scheduler support are included in the core launch workflow across plans.
Visibility
Activity, notifications, and realtime progress
ForgedBase keeps infrastructure work observable through dashboard activity, per-resource feeds, provisioning progress, deployment state, billing notices, integration status, and Reverb-powered updates.
Activity feed
Review provider syncs, server provisioning, site creation, domain routing, SSL work, deployment results, maintenance actions, and key sync events.
Provisioning pills
Track queued, running, failed, retrying, completed, and skipped states from the page where the work matters.
Realtime updates
Broadcast events and Echo listeners keep progress moving without manual refreshes when queues and Reverb are running.
Email notices
Workspace invitation, integration connection, billing, server provisioned, site provisioned, and credential emails keep important outcomes visible.
Operational notes
Realtime event names, channel names, payload keys, listener names, and progress order are treated as high-risk behavior and preserved carefully.
If a status appears stuck, check queue workers, failed jobs, and whether the page is listening to the expected realtime updates.
Dashboard indicators are intentionally practical: they show the next useful state rather than decorative progress.
Notifications
Integrations
Integrations connect deployment, file transfer, and workspace events to the places your team already watches. Availability is plan-aware and workspace-scoped.
Slack
Connect Slack through OAuth and use it for site notifications and workspace event delivery.
Discord
Connect Discord through OAuth for site notifications where enabled by the workspace plan.
Telegram
Create Telegram destinations with a bot token and chat ID after validating the bot and target chat.
Webhooks and ClickSend
Send signed webhook deliveries to custom endpoints or configure ClickSend SMS recipients for high-signal site alerts.
Operational notes
Integrations can be tested or validated before saving where the provider supports a meaningful test delivery.
Site notification settings choose which connected destinations receive deployment success and failure events.
Free workspaces include Slack access; paid plans unlock all integrations configured in billing.
Collaboration
Teams and permissions
Workspace collaboration is role-based so infrastructure, site, access, integration, billing, and team management tasks can be assigned without sharing ownership credentials.
Workspace switching
Move between workspaces from the dashboard while keeping resources scoped to the active workspace owner.
Invitations
Invite team members with tokenized acceptance links and send invitation or removal emails as membership changes.
Roles
Use Admin, Developer, Operator, Viewer, or Custom roles to shape provider, server, site, access, integration, and account permissions.
Permission checks
Create, manage, delete, command, domain, backup, SFTP, deploy key, integration, team, and settings permissions gate sensitive actions.
Operational notes
Pro includes limited team access, while Enterprise removes the team member limit.
Billing-sensitive settings remain owner-aware even when an admin can manage most workspace resources.
Viewer access is read-only across providers, storage providers, servers, sites, and integrations.
Plans
Billing and resource limits
Billing controls workspace capacity while keeping the core launch workflow consistent. Stripe handles checkout, subscription changes, invoices, payment methods, refunds, and billing portal access.
Free
One server and one site with SSL certificates, subdomains, push to deploy, Slack integration, deployment history, scheduler, and queue workers. No card is required.
Pro
Two servers, unlimited sites, database backups, team collaboration, and all integrations for growing client projects.
Enterprise
Unlimited servers, unlimited sites, unlimited team members, backups, collaboration, and all integrations for production workspaces.
Limit handling
When a workspace reaches capacity, existing resources stay recorded and ForgedBase blocks new over-limit actions with upgrade guidance.
Operational notes
Plan changes are confirmed through Stripe before ForgedBase updates workspace access.
Downgrades do not delete servers, sites, domains, deployments, or team records.
Billing webhooks update subscription state and notify the workspace owner when payment attention is needed.
Recovery
Troubleshooting
Most operational questions can be answered by checking the resource status pill, the latest run, the activity feed, provider metadata, queue health, and any detailed failure message on the relevant page.
Provider not ready
Confirm the provider is connected, not currently syncing, and has synced the metadata required by the form you are using.
Provisioning stuck
Check that queue workers are running, Reverb is connected for live updates, and the latest provisioning or maintenance run has not failed.
Domain or SSL issue
Review DNS records, provider DNS zone results, certificate challenge state, rate-limit messages, and whether the domain points at the selected server or site.
Deployment failed
Open the selected deploy run, read the log, confirm source control access, deploy key state, branch or tag selection, and deployment script behavior.
Operational notes
The page where an action starts is usually the best first place to inspect its status.
Failed jobs and activity records carry context that a compact status pill cannot show.
When a provider or realtime feature is involved, avoid changing event names, payload keys, or step order while debugging.
Ready to launch from the dashboard?
Create a workspace, connect a provider, and follow the guided flow from server provisioning through a live site.