Activity Log

The activity log records every significant action taken in your organisation. It provides an audit trail of who did what and when, helping you track changes, investigate issues, and maintain accountability.

Updated 8 Jun 20262 min read

The activity log records every significant action taken in your organisation. It provides an audit trail of who did what and when, helping you track changes, investigate issues, and maintain accountability.

What is logged

Every create, update, delete, and terminate action on your resources is recorded:

ResourceTracked actions
OrganisationCreated, updated, deleted
ProjectCreated, updated, deleted
ContainerCreated, updated, terminated
MemcachedCreated, updated, terminated
RegistryCreated, updated, deleted
SecretCreated, updated, deleted
UserAdded, role changed, removed
BillingTop-ups, payment method changes

What each entry contains

Each activity log entry includes:

  • Summary — A human-readable description (e.g. "Container my-api created").
  • Resource — The type and name of the affected resource.
  • Action — What happened (create, update, delete, terminate).
  • Actor — Who performed the action (user name) or "system" for automated actions.
  • Timestamp — When the action occurred.
  • Project — Which project the resource belongs to (if applicable).

Where to find it

Organisation activity

Go to your organisation dashboard. The activity feed shows the most recent actions across all projects and resources in the organisation.

User activity

Your personal activity feed (accessible from the user menu) shows actions you have performed across all organisations you belong to.

How long activity is retained

Activity log entries are stored permanently. There is no retention limit — you can always go back and review past actions.

Automated actions

Some actions are performed by the system rather than a user. These appear with "system" as the actor. Examples:

  • Containers terminated as part of an organisation or project deletion.
  • Resources cleaned up due to billing suspension.

Tips

  • Use the activity log to verify that a deployment was triggered after you updated a container's image.
  • If something changed unexpectedly, check the activity log to see who made the change and when.
  • The activity log is read-only — entries cannot be edited or deleted.