Usage Analytics 

Motia collects fully anonymized usage analytics to improve developer experience. Your participation is completely voluntary and can be disabled at any time.

Why do we collect usage data?

Since launching Motia, we're seeing incredible adoption across diverse development teams and use cases. However, understanding how developers actually use Motia in real-world scenarios has been challenging to assess through traditional feedback channels alone.

While we actively engage with our community through GitHub discussions, Discord, and direct feedback, these interactions represent only a fraction of our user base. Different teams have varying workflows, constraints, and requirements that may not be reflected in public discussions.

Anonymous usage analytics allows us to understand feature adoption patterns, identify performance bottlenecks, and discover common pain points across our entire user base. This data-driven approach helps us prioritize improvements that benefit the most developers and ensures Motia continues evolving in the right direction.

What information is collected?

We collect basic usage metrics and performance data to understand how Motia is being used. All data is anonymized and aggregated before analysis. Specifically, we track:

  • Command Usage: Patterns for motia build, motia dev, motia cloud deploy
  • Version & Updates: Motia version and update frequency tracking
  • System Environment: CPU count, OS type, CI/CD detection (anonymized)
  • Performance Metrics: Build duration, bundle sizes, cache hit rates
  • Error Patterns: Error frequency and types (without sensitive details)

Privacy and Data Protection

We take your privacy seriously and follow strict data protection principles. All collected data is completely anonymous and cannot be traced back to individual users or organizations.

  • No Sensitive Data: We never collect environment variables, file contents, file paths, source code, or logs.
  • Complete Anonymization: All data is anonymized before transmission.
  • Aggregate Analysis Only: Data is only meaningful in aggregate form to identify trends.
  • No Personal Identification: We cannot identify individual users from collected data.

Our analytics practices are covered under our security disclosure policy. No data we collect is personally identifiable.

How is this data used?

The analytics data helps us make informed decisions about Motia's development roadmap. We use this information internally to identify which features are most valuable, detect performance regressions, understand common workflows, and measure the impact of improvements.

We may share aggregated, non-identifiable insights publicly to demonstrate Motia's growth and adoption trends. This helps the broader development community understand how modern development tools are being used.

Opting Out

You can disable analytics collection at any time by setting an environment variable:

MOTIA_ANALYTICS_DISABLED=true

When analytics is disabled, no data is collected or transmitted. Motia will function identically with analytics disabled.

To verify your analytics status, you can manually go to this address: localhost:3000/motia/analytics/status

If analytics is disabled, you'll see: {"analyticsEnabled":false}

We believe great developer tools are shaped by real-world usage, but only with your consent. Your privacy matters, and your feedback, whether explicit or anonymous, helps Motia become better for everyone.

glow
Footer Background

Use Cases

Integrations

Telemetry
ManifestoDocumentation
wordmark
glow