about

Tuist: company and mission

Tuist builds infrastructure that shortens the build, test, and review loop for developers, CI, and the coding agents working alongside them.

Mission and approach

Automation only moves as fast as the loop it runs in. When builds and tests take minutes or fail unreliably, people lose flow, CI burns time, and agents cannot iterate toward working code. Tuist attacks that loop with shared caching, managed CI compute, test tooling, build and bundle insights, and app previews, adopted one capability at a time on top of the toolchain a team already uses.

Background

Tuist started as an open-source, client-side toolkit for Apple's ecosystem, best known for generating Xcode projects from Swift manifests. It became a company, Tuist GmbH in Berlin, to build infrastructure across build toolchains: today Xcode, Gradle, Bazel, and Elixir integrations, depending on the feature. The founders are Pedro Piñera (CEO) and Marek Fořt (CTO). The team previously built mobile tooling at Shopify and publishes how it works in the [company handbook](https://handbook.tuist.dev).

Which area to evaluate

• Overview and toolchain matrix: [Product overview](/marketing-markdown).
• Repeated compilation: [Cache](/marketing-markdown/cache).
• Managed CI machines next to the cache (invite-only): [Compute](/marketing-markdown/compute).
• Slow or flaky tests: [Tests](/marketing-markdown/tests).
• Sharing development app builds: [Previews](/marketing-markdown/previews).
• Plans and billing: [Pricing](/marketing-markdown/pricing).
• Trust and dependency risk: [Security](/marketing-markdown/security), [Openness](/marketing-markdown/openness), [Longevity](/marketing-markdown/longevity).

Limitations

The mission statement is not a support matrix or a performance guarantee. Use the product guides and documentation for current capabilities, and the live [About page](/about) for the current team.