Skip to main content

Deploy Swetrix

Swetrix is an open-source web and product analytics platform with cookieless tracking, real-time traffic reports and event analytics. Moltern deploys its frontend and API behind one HTTPS URL with managed ClickHouse and Redis.

What Moltern deploys​

ComponentPurposeAccess
Swetrix 5.4Dashboard, account API and event collectorOne public HTTPS URL
Managed ClickHouseTraffic and event recordsPrivate to the selected environment
Managed RedisRuntime cache and coordinationPrivate to the selected environment

The Swetrix application is stateless and does not use the obsolete PostgreSQL layout from older community deployment examples.

Capacity before deployment​

The application request is 100 mCPU and 1 GiB of memory, before ClickHouse and Redis are included. Review the complete install impact and workspace allowance before deploying.

Deploy Swetrix​

  1. Open Services and choose Swetrix.
  2. Select the project and environment.
  3. Enter a service name.
  4. Review the three-workload install impact.
  5. Choose Deploy service.
  6. Wait for the dependencies and Swetrix route to become Running.

Swetrix deployment form in Moltern

Swetrix deployment preview with ClickHouse and Redis dependencies

Create the owner and project​

Open the generated URL:

  1. Register the first user with a work email and strong password.
  2. Complete the short onboarding flow.
  3. Create a project for the website.
  4. Enter its public URL and a recognizable project name.
  5. Copy the generated tracking code.

Collect and verify traffic​

Install the generated tracker in the website and load a controlled page. Open the project traffic summary and confirm that the page-view count increases.

Swetrix project traffic summary retained after a Moltern restart

Use stable project IDs and send only analytics properties your privacy policy permits. Browser privacy tools can block the request even when Swetrix is healthy.

Restart and persistence​

Stopping and starting Swetrix replaces its frontend, API and proxy runtime. The account, project and traffic remain in the managed data services. Sign in after restart and reopen the same project to confirm the lifecycle.

Storage and metering​

Moltern accounts for Swetrix, ClickHouse and Redis independently. Billing reports their CPU, memory, replicas and measured workspace bytes. The Swetrix application does not create a hidden data volume.

Delete Swetrix​

Choose Delete Service, select stored-data removal and confirm the protected action. Moltern removes Swetrix, its auto-provisioned ClickHouse and Redis dependencies, assigned workspace paths, credentials, route and usage allocations.

Troubleshooting​

SymptomWhat to check
Registration returns an API errorConfirm the API container and both dependencies are Running.
The frontend cannot reach /backendReview the service route and proxy logs; frontend and API share one public origin.
Traffic remains at zeroVerify the project ID, tracker request, selected period and browser privacy extensions.
Deployment waits on dependenciesReview ClickHouse and Redis progress before retrying Swetrix.
A project disappears after restartConfirm the original managed dependencies remain attached.

Upstream resources​