Docs

Overview

What this page is for

Fenwave is an internal developer platform: one place to find what your organisation has built, create new services, deploy them across environments, and manage who can do what. This page explains what it is for and where to go next.

If you have five minutes, read this then the Quick Start Guide.

Before you start

You need an account. You cannot create one yourself — an administrator adds you, and you then sign in with GitHub or Bitbucket. Your profile is created on first sign-in.

If you cannot sign in, that is the reason: ask an administrator to add you.

Opening it

Fenwave runs at the URL your organisation provides. The sidebar is the whole product; everything below is reachable from it.

The interface

Every menu group answers a different question.

Menu Answers Start at
Explore What exists, who owns it, what depends on what Catalog
Build How do I create something new Create an Application
Deploy Where is it running, and how do I ship a change Deploy
Cost What is it costing, and what should we change Cost Analysis
Object Storage Where is our bucket data Object Storage
Tools Local setup, scanning, load and test running Tools
Settings Who can do what, and how the platform is configured Settings
My Space My account, my groups, my notifications My Space

You will not see all of these

Each entry is permission-gated. Seeing fewer menu items than a colleague is normal and not a fault — see Access the Platform.

Walkthroughs

Scenario

Your first hour on Fenwave, as a developer joining a team.

  1. Sign in. If it fails, an administrator has not added you, or the email on your record does not match your Git account.
  2. My Space › My Profile — confirm which account you are signed in as, and set your language.
  3. My Space › My Groups — check you are in your team’s group. If not, ask; it affects what you own, not what you can do.
  4. Explore › Catalog — filter by your group’s ownership. This is what your team is responsible for, and it is often more than the induction mentioned.
  5. Explore › Architecture — the same set as a graph, which is the faster way to see how it fits together.
  6. Deploy › Dev — create an ephemeral environment for a branch. Breaking a dev environment costs nothing, which is the point.
  7. Read the Events tab rather than assuming a green deployment means a working application. That single habit saves more time than anything else here.

When it doesn’t work

Symptom Cause How to check Fix
You cannot sign in No account, or the email does not match your Git account — Ask an administrator to add or correct your user record
Most of the menu is missing You hold few permissions My Profile Ask for a role suited to your work
A menu item leads nowhere useful You have access but nothing is configured yet The area’s own page See that area’s troubleshooting table
The platform looks different from these docs These docs describe the current menu — Report it; the docs mirror the sidebar deliberately

Next