Getting Started
Create your Fugoku account and deploy your first instance in minutes
Getting Started with Fugoku Cloud
This guide will walk you through creating your account, setting up billing, and deploying your first compute instance.
Prerequisites
Before you start, you'll need:
- A valid email address
- A payment method (credit card or PayPal)
- Basic familiarity with Linux command line (optional but helpful)
Step 1: Create Your Account
Visit console.fugoku.com/signup and create your account.
- Enter your email address
- Choose a strong password (min 12 characters)
- Verify your email address
- Complete your profile (name, company, country)
You'll receive a verification email within minutes. Click the link to activate your account.
Step 2: Add Payment Information
Navigate to Account → Billing → Payment Methods in the Console.
Fugoku accepts:
- Credit cards (Visa, Mastercard, Amex)
- Debit cards
- PayPal
- Bank transfer (for invoices >$500/month)
Billing Model:
- Compute: Hourly billing, charged per second of usage
- Storage: Monthly billing, prorated daily
- Bandwidth: Per-GB pricing, included allowance with each plan
- Minimum charge: $0.01 (we don't charge for exploration)
New accounts receive $10 credit to test the platform.
Step 3: Generate API Credentials
You can manage Fugoku through the web console, CLI, or API. For CLI and API access, generate credentials:
- Go to Account → API Credentials
- Click Create New Token
- Name your token (e.g., "dev-laptop")
- Copy the token immediately (it won't be shown again)
- Store it securely (password manager recommended)
# Set your token as an environment variable
export FUGOKU_API_TOKEN="fgk_abc123..."
# Or save to CLI config
fugoku auth set-token fgk_abc123...Step 4: Install the CLI (Optional)
The Fugoku CLI provides a fast way to manage infrastructure from your terminal.
Installation:
# Using npm
npm install -g @fugoku/cli
# Using Homebrew (macOS)
brew install fugoku/tap/fugoku-cli
# Using curl (Linux)
curl -sSL https://cli.fugoku.com/install.sh | bashVerify installation:
fugoku version
# Output: Fugoku CLI v1.4.2Authenticate:
fugoku auth login
# Opens browser for OAuth flow
# Or use API token
fugoku auth set-token fgk_abc123...Step 5: Deploy Your First Instance
Let's create a simple Ubuntu VM.
Via Console
- Navigate to Compute → Instances
- Click Create Instance
- Configure:
- Name: my-first-server
- Region: lagos-1
- Plan: standard-2 (2 vCPU, 4GB RAM)
- Image: ubuntu-22.04
- SSH Key: Upload your public key or generate new
- Click Create
Your instance will be ready in 30-60 seconds.
Via CLI
# Upload your SSH key first
fugoku ssh-keys add --name laptop ~/.ssh/id_rsa.pub
# Create instance
fugoku create instance \
--name my-first-server \
--plan standard-2 \
--image ubuntu-22.04 \
--region lagos-1 \
--ssh-key laptop
# Output:
# ✓ Instance created: srv-8x4k9m2n
# IP: 102.89.45.178
# Status: provisioning → running (45s)Via API
curl -X POST https://api.fugoku.com/v1/instances \
-H "Authorization: Bearer $FUGOKU_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "my-first-server",
"plan": "standard-2",
"image": "ubuntu-22.04",
"region": "lagos-1",
"ssh_keys": ["laptop"]
}'Step 6: Connect to Your Instance
Once your instance is running, connect via SSH.
Get Connection Details
Console: Navigate to your instance page for IP address and SSH command
CLI:
# List instances
fugoku instances list
# Get instance details
fugoku instances get my-first-server
# SSH directly (CLI manages keys)
fugoku ssh my-first-serverManual SSH
ssh root@102.89.45.178
# or
ssh ubuntu@102.89.45.178 # depends on imageDefault usernames by image:
- Ubuntu:
ubuntu - Debian:
debian - CentOS/Rocky:
centos - Fedora:
fedora
Step 7: Deploy Your Application
Your instance is a blank canvas. Here's a simple web server setup:
# SSH into your instance
fugoku ssh my-first-server
# Update system
sudo apt update && sudo apt upgrade -y
# Install Nginx
sudo apt install -y nginx
# Start and enable
sudo systemctl start nginx
sudo systemctl enable nginx
# Test
curl localhost
# Output: Welcome to nginx!Visit your instance's IP in a browser: http://102.89.45.178
Step 8: Assign a Floating IP (Optional)
Floating IPs are static addresses that can be reassigned between instances.
# Create floating IP
fugoku networking create-ip --region lagos-1
# Assign to instance
fugoku networking assign-ip \
--instance my-first-server \
--ip 102.89.45.200
# Now use 102.89.45.200 for DNS recordsWhy floating IPs?
- Static address for DNS records
- Zero-downtime failover between instances
- Decouple network identity from compute lifecycle
Step 9: Set Up Backups
Enable automatic snapshots for your instance:
# Enable daily snapshots, keep 7 days
fugoku snapshots enable \
--instance my-first-server \
--schedule daily \
--retention 7Or in the Console: Instance → Snapshots → Enable Automatic
Step 10: Monitor Your Instance
View metrics in the Console or via CLI:
# Get current stats
fugoku instances stats my-first-server
# Output:
# CPU: 12% | RAM: 45% (1.8GB/4GB)
# Disk: 2.1GB/80GB | Network: ↓ 450 Kbps ↑ 120 Kbps
# Uptime: 2h 34mConsole provides:
- CPU, RAM, disk, network graphs (1h, 24h, 7d, 30d)
- Alert configuration (email/SMS when thresholds exceeded)
- Log access (system logs, boot logs)
Common Next Steps
Deploy a Database
# Create instance for PostgreSQL
fugoku create instance \
--name postgres-db \
--plan standard-4 \
--image ubuntu-22.04 \
--region lagos-1
# Install PostgreSQL
fugoku ssh postgres-db
sudo apt update && sudo apt install -y postgresql postgresql-contribSet Up Load Balancing
For production apps, distribute traffic across multiple instances:
# Create load balancer
fugoku lb create \
--name api-lb \
--region lagos-1 \
--algorithm round-robin
# Add backend instances
fugoku lb add-backend api-lb --instance api-1
fugoku lb add-backend api-lb --instance api-2See Load Balancers for details.
Configure Private Networking
Isolate backend services on a private network:
# Create private network
fugoku networks create \
--name backend-net \
--subnet 10.10.0.0/24 \
--region lagos-1
# Attach instances
fugoku networks attach backend-net --instance postgres-db
fugoku networks attach backend-net --instance api-1See Networking for full guide.
Troubleshooting
Can't SSH into instance
Check security group rules:
fugoku firewalls list-rules my-first-serverEnsure port 22 is allowed from your IP.
Add rule if needed:
fugoku firewalls add-rule my-first-server \
--protocol tcp \
--port 22 \
--source 0.0.0.0/0Instance is slow to provision
Typical provisioning time: 30-90 seconds. If >5 minutes:
- Check status:
fugoku instances get my-first-server - View logs: Console → Instance → Logs
- Contact support if stuck: support@fugoku.com
Billing questions
- View usage: Console → Billing → Usage
- Current balance: Console → Billing → Overview
- Invoices: Console → Billing → Invoices
Getting Help
- Documentation: docs.fugoku.com
- API Reference: docs.fugoku.com/api
- Support Email: support@fugoku.com (response <2h)
- Community Discord: discord.gg/fugoku
- Status Page: status.fugoku.com
Next Steps
Now that you have your first instance running:
- Explore the Console - Learn the dashboard
- Browse Instance Types - Find the right size
- Learn about GPU Compute - Train ML models
- Set Up Infrastructure as Code - Automate with Terraform
- Read the API Docs - Build integrations
Welcome to Fugoku Cloud. Build something great.