OrbitsDocs
esc
    Open Orbits
    BillingUsage

    Usage

    What your team and each project used this month, day by day. Requests, bandwidth, build minutes, function runs, deployments and log lines, compared with the month before, with a CSV export.

    The Usage pages

    Team › Usage shows what the whole team used in a month, day by day and project by project. Each project has its own Usage tab with its row of the same figures, split by environment. Any member of the team can see both.

    Pick a month from the period filter: every month from the team's first deployment to now. Days are Lagos days, and today's figures are as of when you opened the page.

    What's measured

    MeasureWhat it counts
    RequestsRequests Orbits' edge sent to the team's deployments, production and previews
    BandwidthBytes the edge sent back in answers, headers included
    Build minutesEach build from start to finish, failed builds included, by the day it was created
    Function runsRequests to projects that run as server functions. Each is also counted in Requests
    DeploymentsDeployments created, by day
    Log linesLines in the projects' runtime logs

    Bandwidth is counted from when Orbits started recording it, so requests before then count as 0 bytes.

    Function runs count a call to the function for each request. Server functions run as one long-lived server for now, so this is a count of requests, not of separate starts.

    Compared with last month

    Each figure is compared with the same days of the month before ("+18% on September"). A team with no deployments before this month has nothing to compare with.

    By project

    By project lists every project the team has, sorted by requests, each with its month's totals and its days. A project's own Usage tab adds By environment (production, preview and development, where there's usage) and how many branches had a preview deployment this month.

    Deleted projects keep counting in the team's totals, in a row of their own, after the project is gone.

    When figures are missing

    Requests, bandwidth, function runs and log lines come from the runtime logs. If those can't be read for a moment, the page shows them as unavailable rather than as zero. Builds and deployments still count.

    Daily usage is kept for 400 days. The runtime logs themselves are kept for 7 days.

    Usage and your plan

    Orbits doesn't charge by usage: Free and Pro are flat. The Usage pages are there so you can see what your projects do. The plan's limits are on limits.

    Export

    Team › Usage and a project's Usage tab can be downloaded as CSV for the month shown.

    The team overview

    The team's home page shows a short version over the last 24 hours, 7 days or 30 days: deployments (against the range before), the average build time of those that went ready, requests (and this month's so far, since midnight on the 1st in Lagos), and projects whose latest deployment failed.

    From the CLI and the API

    Terminal
    $ orbits usage$ orbits usage --month 2026-10

    GET /v1/teams/{team}/usage?month=2026-10 returns a month (this month if you leave month out; a month still to come is 422):

    Field
    totals, previousThe month's requests, bandwidth_bytes, build_minutes (one decimal place), function_runs, deployments and log_lines, and the same days of the month before (or null)
    dailyEach day's totals
    by_projectEach project's totals, days, by_environment and preview_branches, most requests first
    deleted_projectsProjects deleted since, counted in totals only
    monthsEvery month from the first deployment, newest first
    logs_availablefalse while the log figures can't be read; show them as unavailable

    GET /v1/teams/{team}/overview?range=7d is the overview. See API › Usage and activity.

    Was this page helpful?

    Updated