Banuba

Name: Banuba
Brand: Banuba

The most immersive Face AR technology for brands and developers.

Est 2016|Raised $12M|38 Ref Customers

LinkedIn 5K|Web traffic 62K|FTEs 80|HQ Holly Springs, North Carolina, US

Published Oct 15, 2026

01Common complaints

- Organizations that require fully self-serve, publicly listed developer pricing for AR SDKs may prefer vendors with clear tiered pricing to reduce procurement time. - Organizations with strict compliance requirements that mandate documented SOC 2/ISO 27001 evidence prior to evaluation may find vendor materials insufficient and should seek providers with verifiable certifications. - Teams that require minimal integration effort and prefer a managed widget for web-first deployments may find more turnkey competitor widgets easier to adopt. - Organizations seeking to avoid potential vendor lock-in and wishing to retain full long-term control over the AR/video pipeline may prefer an in-house solution built on ARKit/ARCore and custom ML models. - Projects that only require a narrow feature set (for example, simple face filters) may find lighter-weight SDKs or open-source alternatives more cost-effective.

Documented or observable limitations

Security certifications such as SOC 2 or ISO 27001 were not clearly documented in public materials reviewed.
Core SDK pricing typically requires sales engagement, which can increase procurement time.
Platform and toolchain requirements (e.g., modern iOS versions, Xcode versions, architecture support) can complicate CI/testing or legacy app support.

Roadmap and updates

Banuba publishes SDK update notes on its blog and documentation; consolidated public roadmap timelines are not consistently available.

02Why they buy

Strengths validated by evidence (not just marketing)

- Multi-platform engineering support and samples: Banuba maintains integration samples for iOS, Android, Flutter, and React Native, which can reduce initial integration effort. - Breadth of the camera stack: Banuba provides Face AR, Video Editing, and Virtual Try-On components, enabling a single vendor solution for multiple camera-related features. - On-device processing posture: Banuba emphasizes on-device processing for certain SDK functionality and states that it does not collect camera content for some products; this claim should be validated in technical review and contracts.

Where competitors may have advantages

Some competitors provide clearer commercial packaging and published pricing for certain try-on offerings and may offer more retail-oriented tooling.
Platform providers with large creator ecosystems may provide continuously refreshed effect libraries that are useful for specific distribution strategies.
Some alternatives may have more readily available enterprise security collateral.

03Field reports

Review platforms (G2, Trustpilot, etc.)

G2 (vendor page; limited review volume) - Positive themes include the breadth of AR features (2D/3D stickers, tracking, beautification) and a wide set of capabilities. - Limitations: review volume is limited and some reviews may be vendor-invited, affecting representativeness. Trustpilot (very low volume) - Some positive feedback references SDK behavior and instances of responsive support; overall volume is small. Sitejabber (mixed) - Reviews vary: some cite delayed support responses and dissatisfaction with pricing and integration, while others are uneven in format and usefulness.

Community / social signals

Official integration samples and documentation exist. Community discussion volume on general developer forums appears limited compared with more mainstream developer platforms.

Reasons customers selected Banuba (recurring themes)

Based on vendor materials and review snippets:

Cross-platform SDK availability (native plus Flutter/React Native samples).
Reduced time-to-market compared with building AR/video pipelines entirely in-house.
A bundled set of camera, AR, and editing features available from a single vendor.

Reasons for complaints or churn drivers (themes)

From third-party reviews and common SDK buyer issues:

Integration friction: documentation gaps and implementation complexity are cited.
Support responsiveness: reports vary, with some customers describing timely support and others reporting slow response.
Pricing transparency: quote-based SDK pricing can be a procurement barrier for smaller teams.

Vendor-published case study: a beauty brand — reported event results

- The vendor’s case study describes a beauty brand pre-launch event that generated significant revenue, with large audiences, many try-on sessions, and numerous product sales tied to the virtual-try-on experience. Critical evaluation: - This is a vendor-published case study and the methodology is not independently audited. - Event performance is influenced by influencer reach, marketing execution, and product-market fit, not only the virtual-try-on feature. - The case study indicates the vendor can be used in high-volume campaigns and handled large session volumes in that implementation.

Press-release style case study: video calling app for a large electronics manufacturer

A press-distributed announcement describes integration of the Face Filters SDK into a conferencing app with projected large-scale device deployment.

Critical evaluation:

This is press-distributed material; end-user satisfaction, retention, and measured ROI are not independently validated in public sources.
It suggests the vendor can be deployed at sizable enterprise scale but does not provide independent performance measurement.

04Best fit

Company size

Mid-market to enterprise product teams that can support SDK integration work.
eCommerce brands ranging from SMBs using the self-serve app to larger retailers needing custom integration.

Industries / verticals

Beauty and cosmetics (virtual makeup try-on).
Eyewear, jewelry, and fashion accessories (try-on).
Social/UGC apps and creator tools (video editing and effects).
Video conferencing and communication apps (background segmentation, beautification).

Roles and personas

Economic buyer: Head of Product, CTO/VP Engineering, eCommerce Director.
Champions: Mobile/web engineering leads, growth or product managers focused on engagement and try-on ROI.
Users: end-consumers (try-on/video creation) and internal merchandising/content teams.

Fit qualifiers

A good fit when:

Production-quality AR features are needed without building core computer-vision and graphics pipelines internally.
Multi-platform support is required (native and cross-platform frameworks).
The organization can accept vendor-provided SDK updates and manage mobile releases.

Disqualifiers

Not a good fit when:

The organization requires publicly verified security certifications before vendor engagement.
Fully transparent, self-serve pricing is required for SDKs without sales engagement.
Support for very old OS or toolchain versions is required.

05The pitch

What the product does (objective core value proposition)

Banuba is a B2B augmented reality (AR) and AI software vendor that provides SDKs and ready-made components for adding camera-based AR experiences to mobile, web, and desktop products. The company’s core offerings center on: - Face AR SDK: face tracking, filters, beautification, background segmentation, virtual try-on, and related real-time effects. - Video Editor SDK: an embeddable short video editor (with effects, AR overlays, captions, etc.) intended for apps that want native video creation. - TINT Virtual Try-On platform: virtual-try-on functionality for eCommerce (notably cosmetics and eyewear) offered via plugins and platform integrations. In practice, Banuba provides camera-related software components and UI elements that product teams can integrate rather than build in-house.

Target market and market positioning

Target buyers tend to be: - Product teams and engineering organizations building consumer apps (UGC/social, creator tools, video apps) that need embedded editing and AR features. - eCommerce and retail brands and platform implementers who want virtual-try-on to improve conversion and reduce returns. - Some enterprise video/communications solutions who want enhancements such as background replacement and face touch-up. Positioning themes observed in public materials emphasize: - Pre-built SDK modules intended for integration to reduce in-house development time. - MAU/usage-based or platform-based licensing depending on the product. - Multi-platform support (native and cross-platform).

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

Download full report →

Published Oct 15, 2026

01Common complaints

Organizations that require fully self-serve, publicly listed developer pricing for AR SDKs may prefer vendors with clear tiered pricing to reduce procurement time.
Organizations with strict compliance requirements that mandate documented SOC 2/ISO 27001 evidence prior to evaluation may find vendor materials insufficient and should seek providers with verifiable certifications.
Teams that require minimal integration effort and prefer a managed widget for web-first deployments may find more turnkey competitor widgets easier to adopt.
Organizations seeking to avoid potential vendor lock-in and wishing to retain full long-term control over the AR/video pipeline may prefer an in-house solution built on ARKit/ARCore and custom ML models.
Projects that only require a narrow feature set (for example, simple face filters) may find lighter-weight SDKs or open-source alternatives more cost-effective.

Documented or observable limitations

Security certifications such as SOC 2 or ISO 27001 were not clearly documented in public materials reviewed.
Core SDK pricing typically requires sales engagement, which can increase procurement time.
Platform and toolchain requirements (e.g., modern iOS versions, Xcode versions, architecture support) can complicate CI/testing or legacy app support.

Roadmap and updates

Banuba publishes SDK update notes on its blog and documentation; consolidated public roadmap timelines are not consistently available.

02Why they buy

Strengths validated by evidence (not just marketing)

Multi-platform engineering support and samples: Banuba maintains integration samples for iOS, Android, Flutter, and React Native, which can reduce initial integration effort.
Breadth of the camera stack: Banuba provides Face AR, Video Editing, and Virtual Try-On components, enabling a single vendor solution for multiple camera-related features.
On-device processing posture: Banuba emphasizes on-device processing for certain SDK functionality and states that it does not collect camera content for some products; this claim should be validated in technical review and contracts.

Where competitors may have advantages

Some competitors provide clearer commercial packaging and published pricing for certain try-on offerings and may offer more retail-oriented tooling.
Platform providers with large creator ecosystems may provide continuously refreshed effect libraries that are useful for specific distribution strategies.
Some alternatives may have more readily available enterprise security collateral.

03Field reports

Review platforms (G2, Trustpilot, etc.)

G2 (vendor page; limited review volume)

Positive themes include the breadth of AR features (2D/3D stickers, tracking, beautification) and a wide set of capabilities.
Limitations: review volume is limited and some reviews may be vendor-invited, affecting representativeness.

Trustpilot (very low volume)

Some positive feedback references SDK behavior and instances of responsive support; overall volume is small.

Sitejabber (mixed)

Reviews vary: some cite delayed support responses and dissatisfaction with pricing and integration, while others are uneven in format and usefulness.

Community / social signals

Official integration samples and documentation exist. Community discussion volume on general developer forums appears limited compared with more mainstream developer platforms.

Reasons customers selected Banuba (recurring themes)

Based on vendor materials and review snippets:

Cross-platform SDK availability (native plus Flutter/React Native samples).
Reduced time-to-market compared with building AR/video pipelines entirely in-house.
A bundled set of camera, AR, and editing features available from a single vendor.

Reasons for complaints or churn drivers (themes)

From third-party reviews and common SDK buyer issues:

Integration friction: documentation gaps and implementation complexity are cited.
Support responsiveness: reports vary, with some customers describing timely support and others reporting slow response.
Pricing transparency: quote-based SDK pricing can be a procurement barrier for smaller teams.

Vendor-published case study: a beauty brand — reported event results

The vendor’s case study describes a beauty brand pre-launch event that generated significant revenue, with large audiences, many try-on sessions, and numerous product sales tied to the virtual-try-on experience.

Critical evaluation:

This is a vendor-published case study and the methodology is not independently audited.
Event performance is influenced by influencer reach, marketing execution, and product-market fit, not only the virtual-try-on feature.
The case study indicates the vendor can be used in high-volume campaigns and handled large session volumes in that implementation.

Press-release style case study: video calling app for a large electronics manufacturer

A press-distributed announcement describes integration of the Face Filters SDK into a conferencing app with projected large-scale device deployment.

Critical evaluation:

This is press-distributed material; end-user satisfaction, retention, and measured ROI are not independently validated in public sources.
It suggests the vendor can be deployed at sizable enterprise scale but does not provide independent performance measurement.

04Best fit

Company size

Mid-market to enterprise product teams that can support SDK integration work.
eCommerce brands ranging from SMBs using the self-serve app to larger retailers needing custom integration.

Industries / verticals

Beauty and cosmetics (virtual makeup try-on).
Eyewear, jewelry, and fashion accessories (try-on).
Social/UGC apps and creator tools (video editing and effects).
Video conferencing and communication apps (background segmentation, beautification).

Roles and personas

Economic buyer: Head of Product, CTO/VP Engineering, eCommerce Director.
Champions: Mobile/web engineering leads, growth or product managers focused on engagement and try-on ROI.
Users: end-consumers (try-on/video creation) and internal merchandising/content teams.

Fit qualifiers

A good fit when:

Production-quality AR features are needed without building core computer-vision and graphics pipelines internally.
Multi-platform support is required (native and cross-platform frameworks).
The organization can accept vendor-provided SDK updates and manage mobile releases.

Disqualifiers

Not a good fit when:

The organization requires publicly verified security certifications before vendor engagement.
Fully transparent, self-serve pricing is required for SDKs without sales engagement.
Support for very old OS or toolchain versions is required.

05The pitch

What the product does (objective core value proposition)

Face AR SDK: face tracking, filters, beautification, background segmentation, virtual try-on, and related real-time effects.
Video Editor SDK: an embeddable short video editor (with effects, AR overlays, captions, etc.) intended for apps that want native video creation.
TINT Virtual Try-On platform: virtual-try-on functionality for eCommerce (notably cosmetics and eyewear) offered via plugins and platform integrations.

In practice, Banuba provides camera-related software components and UI elements that product teams can integrate rather than build in-house.

Target market and market positioning

Target buyers tend to be:

Product teams and engineering organizations building consumer apps (UGC/social, creator tools, video apps) that need embedded editing and AR features.
eCommerce and retail brands and platform implementers who want virtual-try-on to improve conversion and reduce returns.
Some enterprise video/communications solutions who want enhancements such as background replacement and face touch-up.

Positioning themes observed in public materials emphasize:

Pre-built SDK modules intended for integration to reduce in-house development time.
MAU/usage-based or platform-based licensing depending on the product.
Multi-platform support (native and cross-platform).

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

Download full report →