Fixposition

Name: Fixposition
Brand: Fixposition

Precise Global Positoning Everywhere - enable autonomy at scale.

Est 2017|Valuation $23.2M|Raised $10.6M|7 Ref Customers

LinkedIn 5K|Web traffic 13K|FTEs 28|HQ Zurich, Zurich, CH

Published Aug 14, 2026

01Common complaints

- Core missions operate in dark or feature-poor environments (for example, unlit tunnels or night-only operations) where camera-based odometry cannot function and GNSS may be absent. - The deployment requires guaranteed startup in GNSS-denied locations without access to an RTK fix at initialization; the vendor documents a requirement for an RTK fix for initialization in current product versions. - The procurement process requires extensive third-party validation and independent analyst evaluations that are not available publicly; in such cases plan to conduct independent benchmarks and data collection. - The project requires a purely software licensing model with minimal additional sensors; the primary offering is a sensor module/kit with associated integration work. - Cost-sensitive deployments that operate primarily in open-sky conditions where a simple RTK receiver plus corrections subscription would meet requirements at lower total cost.

Disqualifiers (poor fit)

Operations that require guaranteed cold-start performance in GNSS-denied conditions without any RTK fix available at initialization.
Missions that operate primarily in complete darkness where no GNSS is available.
Procurement requirements that mandate full public enterprise security and compliance documentation without willingness to engage in vendor security discovery under NDA.

Publicly acknowledged / documented limitations

Initialization requires a GNSS-RTK fix in current product versions.
Performance can degrade in complete darkness if GNSS is not available.
Drift during GNSS outages is described by the vendor at approximately 0.5–1% of distance traveled.

Integration limitations / operational constraints

Firmware and driver compatibility must be managed; the ROS driver has major tag dependencies on firmware versions.
Typical lead times cited in public materials are 3–6 weeks, which should be included in procurement planning.

Roadmap signals

The vendor has stated intentions to expand startup availability in GNSS-degraded environments; no firm dates were provided in publicly reviewed materials.

02Why they buy

Differentiators supported by available evidence

Integrated vision-aided sensor fusion: the solution combines GNSS RTK, IMU, and camera-based odometry in one packaged module.
Developer-focused integration: the vendor maintains open-source ROS drivers for ROS1 and ROS2 with documentation and migration guidance.
Ecosystem integrations: public partner relationships and component selections (for example, RTK correction partnerships and GNSS receiver choices) indicate an integrated supply-chain approach.

Claims requiring independent verification

Vendor statements asserting parity or superiority to high-end RTK/INS systems and claims about an exceptional performance-to-price ratio should be validated with standardized tests and third-party data.

Areas where competitors may have an advantage

Public enterprise security and compliance documentation and longer track records for some incumbents.
Broader installed base visibility and formal support guarantees from larger GNSS/INS vendors.

03Field reports

Review-platform coverage gap (important)

The vendor does not appear to have substantial listings on mainstream B2B review platforms (G2, Capterra, TrustRadius) based on the searches performed. Independent review-platform evidence is therefore limited. To provide additional perspective this report uses: - Vendor-published customer statements (marketing materials) - Developer community sources (public driver repositories and documentation) for integration observations - Employer-review sites as indirect signals of company operational maturity

Vendor-published testimonials (vendor-sourced)

The vendor publishes customer statements on its website and marketing materials. Examples include curated statements from partner-company leadership noting perceived capabilities and cost considerations; these items do not include independent test methodologies or raw data.

Community/developer signals (mixed/neutral)

The vendor maintains open-source ROS1/ROS2 drivers with compatibility notes and migration guidance, indicating emphasis on developer integration support.
The ROS driver introduced backward-incompatible changes at a major tag, which requires product teams to manage firmware/driver version coupling.

Employee (employer-review) feedback (indirect, mixed)

Reported positives: access to leadership, international environment, and perceived growth opportunities.
Reported challenges: constrained resources and maturing processes consistent with startup scaling.

Common reasons customers select the vendor (inferred from public materials)

Need for position/pose continuity in environments with intermittent GNSS availability.
Availability of evaluation kits and ROS drivers to accelerate testing.
Vendor-supported correction-service options and distributor availability.

Potential churn drivers (hypotheses, not confirmed)

Cost relative to simpler RTK-only setups where those meet requirements.
Vision-based performance degradation in low-light or low-feature environments.
Integration and version-management burden.

Vendor-published case summaries

The vendor publishes customer stories and partner case references involving a range of robotics integrators and manufacturers. What is useful: - These items indicate commercial and technical engagement with multiple robotics companies and demonstrate real-world deployments in outdoor contexts. What is missing / methodology gaps: - Case descriptions generally lack reproducible metrics (for example, error distributions, duration, GNSS conditions during tests, lighting conditions, and ground-truth systems used). Claims of parity with high-end RTK/INS systems are anecdotal without side-by-side logged comparisons.

Partnership-based validation signals

Public partnership announcements (for example, integrations with correction services and component suppliers) validate ecosystem relationships and supply-chain choices, but they do not replace independent performance verification.

04Best fit

Organization size

Typical fit: robotics and autonomy manufacturers or integrators with dedicated navigation or perception engineering resources. Many adopters appear to be small-to-mid organizations engaged in autonomous product development.

Industries / verticals

Agriculture (tractors, sprayers, orchard operations)
Landscaping and robotic lawncare
Utility and municipal robots (sweepers, patrol units)
Industrial outdoor automation (construction, mining, survey where GNSS is intermittent)

Roles / personas

Decision makers: VP Engineering, Head of Autonomy, Product Lead for robotics
End users: Localization/Navigation engineers, Systems integrators, Field test engineers

Problems addressed

GNSS multipath and occlusion that cause RTK drops
Need for position and heading continuity at low speeds in outdoor settings
Desire for an integrated sensor module and reference drivers to accelerate evaluation and validation

Qualification criteria (good fit)

The organization operates in environments with intermittent GNSS and can benefit from camera-based aiding.
The organization can mount and maintain cameras and perform on-site validation in representative terrain.
The organization prefers a packaged sensor and interface rather than building a full custom fusion stack from the ground up.

05The pitch

What the product does (objective value proposition)

Fixposition provides positioning solutions centered on the Vision-RTK 2 sensor. The product fuses GNSS RTK, IMU, and camera-based visual odometry to produce near real-time global position and pose for robotic and vehicle platforms. The fusion approach is intended to maintain position accuracy in environments where GNSS is degraded or intermittently unavailable (for example, under tree canopy, near buildings, or underpasses). Vendor-stated characteristics: the system is described by the vendor as exhibiting distance-dependent drift (in contrast to time-dependent drift reported for some IMU-dominant GNSS/INS approaches). The vendor also states objectives of simplified integration and deployment compared with building a custom fusion solution.

Target market and market positioning

- Primary users: robotics and autonomy engineering teams developing outdoor-capable systems requiring persistent localization. - Typical applications referenced by the vendor: autonomous lawnmowers, agricultural robots/tractors, outdoor mobile robots, utility robots (e.g., sweepers), off-road vehicles, and other industrial outdoor automation. - Market positioning (vendor-stated): the product is positioned as approaching the performance of high-end RTK/INS systems while targeting a favorable performance-to-price profile and improved resilience where GNSS is unreliable.

Get a comprehensive analysis of Fixposition including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Aug 14, 2026

01Common complaints

Core missions operate in dark or feature-poor environments (for example, unlit tunnels or night-only operations) where camera-based odometry cannot function and GNSS may be absent.
The deployment requires guaranteed startup in GNSS-denied locations without access to an RTK fix at initialization; the vendor documents a requirement for an RTK fix for initialization in current product versions.
The procurement process requires extensive third-party validation and independent analyst evaluations that are not available publicly; in such cases plan to conduct independent benchmarks and data collection.
The project requires a purely software licensing model with minimal additional sensors; the primary offering is a sensor module/kit with associated integration work.
Cost-sensitive deployments that operate primarily in open-sky conditions where a simple RTK receiver plus corrections subscription would meet requirements at lower total cost.

Disqualifiers (poor fit)

Operations that require guaranteed cold-start performance in GNSS-denied conditions without any RTK fix available at initialization.
Missions that operate primarily in complete darkness where no GNSS is available.
Procurement requirements that mandate full public enterprise security and compliance documentation without willingness to engage in vendor security discovery under NDA.

Publicly acknowledged / documented limitations

Initialization requires a GNSS-RTK fix in current product versions.
Performance can degrade in complete darkness if GNSS is not available.
Drift during GNSS outages is described by the vendor at approximately 0.5–1% of distance traveled.

Integration limitations / operational constraints

Firmware and driver compatibility must be managed; the ROS driver has major tag dependencies on firmware versions.
Typical lead times cited in public materials are 3–6 weeks, which should be included in procurement planning.

Roadmap signals

The vendor has stated intentions to expand startup availability in GNSS-degraded environments; no firm dates were provided in publicly reviewed materials.

02Why they buy

Differentiators supported by available evidence

Integrated vision-aided sensor fusion: the solution combines GNSS RTK, IMU, and camera-based odometry in one packaged module.
Developer-focused integration: the vendor maintains open-source ROS drivers for ROS1 and ROS2 with documentation and migration guidance.
Ecosystem integrations: public partner relationships and component selections (for example, RTK correction partnerships and GNSS receiver choices) indicate an integrated supply-chain approach.

Claims requiring independent verification

Vendor statements asserting parity or superiority to high-end RTK/INS systems and claims about an exceptional performance-to-price ratio should be validated with standardized tests and third-party data.

Areas where competitors may have an advantage

Public enterprise security and compliance documentation and longer track records for some incumbents.
Broader installed base visibility and formal support guarantees from larger GNSS/INS vendors.

03Field reports

Review-platform coverage gap (important)

To provide additional perspective this report uses:

Vendor-published customer statements (marketing materials)
Developer community sources (public driver repositories and documentation) for integration observations
Employer-review sites as indirect signals of company operational maturity

Vendor-published testimonials (vendor-sourced)

Community/developer signals (mixed/neutral)

The vendor maintains open-source ROS1/ROS2 drivers with compatibility notes and migration guidance, indicating emphasis on developer integration support.
The ROS driver introduced backward-incompatible changes at a major tag, which requires product teams to manage firmware/driver version coupling.

Employee (employer-review) feedback (indirect, mixed)

Reported positives: access to leadership, international environment, and perceived growth opportunities.
Reported challenges: constrained resources and maturing processes consistent with startup scaling.

Common reasons customers select the vendor (inferred from public materials)

Need for position/pose continuity in environments with intermittent GNSS availability.
Availability of evaluation kits and ROS drivers to accelerate testing.
Vendor-supported correction-service options and distributor availability.

Potential churn drivers (hypotheses, not confirmed)

Cost relative to simpler RTK-only setups where those meet requirements.
Vision-based performance degradation in low-light or low-feature environments.
Integration and version-management burden.

Vendor-published case summaries

The vendor publishes customer stories and partner case references involving a range of robotics integrators and manufacturers.

What is useful:

These items indicate commercial and technical engagement with multiple robotics companies and demonstrate real-world deployments in outdoor contexts.

What is missing / methodology gaps:

Case descriptions generally lack reproducible metrics (for example, error distributions, duration, GNSS conditions during tests, lighting conditions, and ground-truth systems used). Claims of parity with high-end RTK/INS systems are anecdotal without side-by-side logged comparisons.

Partnership-based validation signals

Public partnership announcements (for example, integrations with correction services and component suppliers) validate ecosystem relationships and supply-chain choices, but they do not replace independent performance verification.

04Best fit

Organization size

Typical fit: robotics and autonomy manufacturers or integrators with dedicated navigation or perception engineering resources. Many adopters appear to be small-to-mid organizations engaged in autonomous product development.

Industries / verticals

Agriculture (tractors, sprayers, orchard operations)
Landscaping and robotic lawncare
Utility and municipal robots (sweepers, patrol units)
Industrial outdoor automation (construction, mining, survey where GNSS is intermittent)

Roles / personas

Decision makers: VP Engineering, Head of Autonomy, Product Lead for robotics
End users: Localization/Navigation engineers, Systems integrators, Field test engineers

Problems addressed

GNSS multipath and occlusion that cause RTK drops
Need for position and heading continuity at low speeds in outdoor settings
Desire for an integrated sensor module and reference drivers to accelerate evaluation and validation

Qualification criteria (good fit)

The organization operates in environments with intermittent GNSS and can benefit from camera-based aiding.
The organization can mount and maintain cameras and perform on-site validation in representative terrain.
The organization prefers a packaged sensor and interface rather than building a full custom fusion stack from the ground up.

05The pitch

What the product does (objective value proposition)

Vendor-stated characteristics: the system is described by the vendor as exhibiting distance-dependent drift (in contrast to time-dependent drift reported for some IMU-dominant GNSS/INS approaches). The vendor also states objectives of simplified integration and deployment compared with building a custom fusion solution.

Target market and market positioning

Primary users: robotics and autonomy engineering teams developing outdoor-capable systems requiring persistent localization.
Typical applications referenced by the vendor: autonomous lawnmowers, agricultural robots/tractors, outdoor mobile robots, utility robots (e.g., sweepers), off-road vehicles, and other industrial outdoor automation.
Market positioning (vendor-stated): the product is positioned as approaching the performance of high-end RTK/INS systems while targeting a favorable performance-to-price profile and improved resilience where GNSS is unreliable.

Get a comprehensive analysis of Fixposition including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →