Seam Review: API Features, Pricing, Pros & Cons

Profile image for Katie Kistler
Katie Kistler
Updated 17 min read
Resident uses the ButterflyMX Yale offline lock integration to unlock their unit door.
Used by more than 1 million, including the most trusted names in real estate
related-logo-png lincon-property-logo-png lennar-logo-png CA-ventures-logo bozzuto-logo-png

Key takeaways:

  • Seam provides APIs, SDKs, a dashboard, and reusable components that connect software to third-party locks, access systems, thermostats, sensors, and cameras; it is not a turnkey resident-access product.
  • Seam pricing starts at $10 per month and uses credits; its published 100-lock example costs about $402.50 per month, while expiring credits and 1.25x overage make forecasting important.
  • Seam lists more than 1,000 devices, but buyers still need to confirm the status, capabilities, and connectivity requirements of every required brand and model.

 

Resident uses the ButterflyMX Yale offline lock integration to unlock their unit door.

Disclaimer: ButterflyMX provides these blog posts to help our customers and potential customers make the right business decisions. Our blog posts are based on the information available to us at the time of writing.

 

Seam is a developer platform for companies that want to connect their software to smart locks and other physical devices without building a separate access control integration for every manufacturer. Product, engineering, and operations teams may consider it for guest access, remote device control, property automation, or a branded access app.

This Seam review explains what the platform does, which devices it supports, how its credit pricing works, and what infrastructure a deployment may require. It also covers reliability feedback, alternatives, and the difference between an API-first product and a broader property access platform.

This guide will answer:

 

Watch how ButterflyMX works:

 

 

What is Seam?

Seam is a cloud API, dashboard, and SDK platform that connects applications to third-party smart locks, access-control systems, thermostats, sensors, and cameras. The Seam platform is middleware, not a lock, intercom, or finished resident app.

Instead of maintaining a separate integration for every device maker, a software company can use Seam as a common layer. That can reduce duplicated integration work, but the customer still needs to build an app or use a partner platform for the end-user experience.

Seam says it was founded in 2020. The company joined the Y Combinator Summer 2020 batch and is based in San Francisco.

 

Is Seam the same as Seam AI on G2?

No. The G2 profile named Seam, including its 4.4 out of 5 rating from eight reviews, describes an unrelated sales-intelligence product. Those reviews do not evaluate the Seam Labs IoT and access API discussed here.

That distinction matters because independent reviews of the correct product are limited. Check the company name and product description before treating any Seam rating as evidence about this platform.

 

How does Seam work, and who is it for?

Seam sits between a customer application and supported physical devices. A development team can use its APIs, SDKs, webhooks, dashboard tools, and interface components to connect accounts, issue credentials, send commands, and receive device events.

For example, an app can request a time-bound PIN or mobile key through Seam. Seam then translates that request into an action supported by the connected lock or access-control system. Available actions depend on the brand, model, firmware, and connection method.

Seam is designed mainly for software platforms, product engineering teams, larger multi-property operators, and teams building device-control tools. It does not provide a native consumer-facing app, so buyers must create an experience or obtain one from a partner.

This creates a build-versus-buy decision. A software company that wants control over its own interface may value Seam. A property operator seeking mobile access, visitor workflows, video intercoms, and access control in a property-focused platform may instead consider a solution such as ButterflyMX.

 

Seam product modules

Seam organizes its capabilities into API families and supporting tools rather than physical product models.

Swipe to compare →

Module Primary function Example use cases Important scope note
Access Grants and Smart Locks API Creates credentials and controls supported locks Guest PINs, mobile keys, scheduled access, and remote lock or unlock Actions vary by connected model
Access Control Systems API and Mobile SDK Connects applications to supported enterprise access systems NFC or BLE mobile credentials and entrance access Credential support depends on the access system
Thermostats API Controls supported thermostat settings Temperature changes, operating modes, and schedules Available controls depend on the device
Cameras API Retrieves supported motion events and clips Camera alerts and event-linked video The API is in beta
Seam Bridge Connects selected legacy or on-premises systems to the cloud Legacy access hardware and Wiegand keypad connections Used only for applicable deployments
Seam Components Adds reusable interface elements to customer applications Device connection and management screens Components support a custom app rather than replacing it

 

Who may be better served by a turnkey platform?

Organizations without product-development resources may be better served by a managed or turnkey access platform. Seam reduces integration work, but it does not remove the need to design an app, define workflows, support users, and manage the connected hardware environment.

One public developer discussion described per-device and code charges as too expensive for a small rental tool. That is one developer’s experience, not a universal cost result, but it shows why smaller operators should compare total software and development costs instead of focusing only on the $10 starting plan.

 

Which devices and connections does Seam support?

Seam lists more than 1,000 devices across hundreds of brands, but catalog size alone does not establish compatibility. Use the Seam supported-device catalog to check every required brand, model, status, action, and connection method.

Seam uses status labels to show integration maturity. Live means an integration is available, Beta means it has a developing scope, Planned means development is expected, and Inquire directs the buyer to contact Seam rather than promising current availability.

Swipe to compare →

Catalog label What it means Buyer implication Examples
Live The integration is available for supported models Check model-level actions before committing Catalog coverage includes brands such as Yale, Schlage, August, Salto, Assa Abloy, and TTLock
Beta The integration or product area is available with a developing scope Decide whether beta status works for the intended workflow Supported Ring, Arlo, UniFi, Reolink, and Tapo cameras are part of the beta Cameras API
Planned The integration is not presented as generally available today Do not base a near-term deployment on planned support without a clear timeline Several security, garage, and access brands are listed as Planned or Inquire
Inquire The buyer must contact Seam about availability Treat support as unresolved until the proposed scope is clear myQ, Alarm.com, Chamberlain, LiftMaster, Allegion, HID, Genetec, Lenel, Level, and Vivint are listed across Inquire or Planned rather than Live

Even a Live integration may not support every function. Remote commands, PIN creation, event data, and mobile credentials depend on manufacturer capabilities and firmware, so teams should create a model-by-model requirements list before signing a contract.

 

Built-in, hub-required, and local-only connectivity

Seam also classifies how devices connect. These labels can affect hardware cost, cloud control, and deployment complexity.

Swipe to compare →

Connectivity label What it means Buyer implication Example
Built-in The device has a direct connection method for the supported integration A separate smart-home hub may not be needed Yale Approach is listed as a built-in Wi-Fi example
Hub required The device depends on a compatible hub to reach cloud services Budget for hub hardware, setup, maintenance, and network placement Many Z-Wave and Zigbee locks
Local only The model has local connectivity that can limit cloud control Remote actions and real-time workflows may not match a cloud-connected model Dormakaba 790, Salto Ælement EU, and Onity Trillium

This distinction matters in retrofits. An existing lock may appear in the catalog but still require a hub, or its local-only connection may not support the remote workflow an application needs.

 

Installation and required hardware

Seam generally does not install physical locks, cameras, intercoms, or access-control equipment. Each device follows its manufacturer’s installation process, after which the customer connects it through account credentials, an API integration, or a Seam Connect Webview.

Internet access is normally required because Seam is a cloud API. Some BLE, Z-Wave, and Zigbee devices need an additional hub, while Seam Bridge can connect selected legacy or on-premises systems. Account for these dependencies in the deployment plan instead of treating API compatibility as a complete installation specification.

 

Seam features and integrations

Seam focuses on cross-brand device control and the developer tools needed to add that control to another application. Its core capabilities combine access credentials, remote actions, device events, reusable interface components, and management tools.

 

Access and automation features

  • Time-bound access: Applications can create scheduled PIN codes or mobile keys on supported devices, helping align guest or resident access with a defined period.
  • Remote commands: Supported integrations can lock or unlock devices without staff being on-site.
  • Webhooks: Applications can receive device events and use them to update another system or trigger a workflow.
  • Physical cards: Supported access-control systems can encode and assign plastic cards.
  • Thermostat and sensor automation: Applications can change supported thermostat settings and use sensor data for workflows such as noise-threshold alerts.
  • Seam Components: Reusable React and HTML components can reduce the work needed to create common device-management screens.
  • Multi-workspace management: Dashboard tools can help teams organize devices across locations and user roles.

Credential support remains device-dependent. Seam can expose PINs, BLE or NFC mobile keys, and card encoding where the underlying system allows them. ButterflyMX takes a different approach by providing mobile access, visitor access, and wallet-based credentials as part of a property access platform, which may better fit operators that do not want to build the user interface themselves.

 

PMS and hospitality integrations

Seam works behind the scenes for property-management and hospitality software. The company identifies Guesty, Hospitable, Hostaway, Lodgify, Cloudbeds, Mews, RMS Cloud, Breezeway, Operto, Enso Connect, Canary, SuiteOp, Akia, and eviivo among its ecosystem.

For end users, the PMS or hospitality platform often supplies the visible workflow while Seam handles compatible device connections in the background. Buyers already using one of these platforms should determine whether access is included through that vendor or whether a separate Seam integration is needed.

 

Camera and AI-agent capabilities

Seam offers a beta Cameras API for retrieving motion events and clips from supported third-party cameras. Because it is an API layer, the customer decides how those events and clips appear in its own application.

Property teams comparing camera options should distinguish this developer workflow from a broader security platform. ButterflyMX supports security cameras and video intercoms within its property access and security platform, while Seam exposes supported third-party camera data for another product to use.

Seam also supports the Model Context Protocol, or MCP, for compatible coding agents such as Claude Code, Cursor, Codex, Gemini CLI, OpenCode, and Mistral Vibe. This can help technical teams configure projects or control connected devices through agent-based development tools, although device and security requirements still apply.

 

How much does Seam cost?

Seam uses monthly credit packages plus per-device and per-action consumption. The public Seam pricing page offers a free entry point for the first device and first API call, followed by self-serve plans starting at $10 per month; enterprise pricing is custom.

A credit is a billing unit. Connecting a device consumes recurring credits, while actions such as creating an access grant or sending a successful lock command use additional credits.

Swipe to compare →

Plan or charge Price or credits Included amount Budget implication
Free entry point $0 First device and first API call Useful for an initial evaluation, not a full fleet estimate
Hobbyist $10 per month 1,000 credits Extra credits cost 1.25 cents each
Pro $96 per month 10,000 credits Extra credits cost 1.2 cents each
Scale $230 per month 25,000 credits Extra credits cost 1.15 cents each
Lock or access device 100 credits per month One connected device Creates a recurring per-device cost before activity
Access grant 30 credits One access grant Frequent guest turnover can increase consumption
Successful lock or unlock command 5 credits One successful command Remote-control volume affects the bill
Physical card encoding 2 credits One encoded card Relevant to supported card-based access systems
Camera 500 credits, or $5 per month One camera with events and alerts Camera count adds recurring consumption
Overage 1.25x the package credit rate Usage above the package Underestimating activity increases the effective rate

Seam publishes 18 credit tiers, from 1,000 to 100 million monthly credits. Unused credits expire at the monthly billing boundary, with a one-time carryover rule tied to upgrades, so buyers need to balance unused capacity against the higher overage rate.

 

What Seam could cost for an active lock fleet

Seam’s published 100-lock example totals about $402.50 per month, or $4.03 per device, under the activity assumptions in its calculator. It is a useful anchor, but not a universal per-lock price: access grants, commands, cameras, and other actions change consumption.

Before selecting a package, estimate connected devices, access grants, remote commands, cards, cameras, and other billable actions for a normal month and a peak month. This helps show whether the greater risk is expiring unused credits or paying the 1.25x overage rate.

One Trustpilot reviewer reported a dispute involving expired prepaid credits and additional charges. That single complaint should not be treated as representative of every customer, but it reinforces the need to understand expiration, renewal, and overage terms before prepaying.

 

Security, reliability, and customer feedback

Seam has completed a SOC 2 Type I audit, but security controls and day-to-day reliability are separate evaluation areas. The SOC 2 announcement says Johanson Group LLP performed the audit.

SOC 2 Type I provides a point-in-time assessment of control design. Enterprise buyers should still assess their own data flows, account permissions, webhook handling, incident processes, and the security posture of connected device manufacturers.

Public SmartThings discussions from 2023 documented account-linking, two-factor authentication, timezone scheduling, and dashboard synchronization problems. The same discussions showed direct founder involvement in troubleshooting and fixes, which is a positive sign of support responsiveness but does not establish current performance for every integration.

Independent review volume remains thin. At the time covered here, Capterra listed zero reviews, while Trustpilot showed a 3.2 out of 5 score based on one review. A pilot using your actual devices will likely be more useful than an aggregate review score.

 

Seam review: pros and cons

Seam offers broad integration coverage and useful developer tools, but the platform also requires engineering work, detailed compatibility checks, and careful usage forecasting.

 

Pros

  • Broad cross-brand device layer: One platform can reduce the number of separate integrations needed for supported locks, access-control systems, thermostats, sensors, and cameras.
  • Public self-serve pricing components: Published plans and unit charges let teams build a preliminary usage model before discussing enterprise terms.
  • Multiple developer surfaces: APIs, SDKs, webhooks, a dashboard, CLI tools, and reusable components support several development workflows.
  • SOC 2 Type I compliance: The completed audit is relevant to companies assessing vendor security controls.
  • Visible hands-on support history: Community discussions show direct founder involvement in resolving technical problems.
  • Emerging AI-agent support: MCP support gives technical teams another way to set up and operate connected devices.

 

Cons

  • Requires engineering resources: Seam is infrastructure, so buyers still need an application, user experience, support process, and product team.
  • Catalog breadth can hide availability gaps: A required brand may be Planned or Inquire rather than Live.
  • Capabilities vary by model: PINs, mobile keys, remote commands, events, and cloud connectivity are not uniform across devices.
  • Credit pricing adds forecasting risk: Unused credits expire, while overage costs 1.25 times the package rate.
  • Some devices require extra infrastructure: Hub-required models add hardware and management needs, while local-only devices may limit cloud workflows.
  • Independent review coverage is limited: Buyers have little broad third-party sentiment data and should not rely on an isolated rating.

 

Seam alternatives

Seam alternatives depend on whether a buyer wants device middleware, a managed access product, a consumer smart-home system, or general integration tools. These options are not feature-equivalent, so the right comparison starts with the operating model you need.

  • RemoteLock: RemoteLock is relevant to buyers seeking a managed hardware-and-software access solution rather than a raw cross-brand API.
  • Samsung SmartThings: SmartThings can suit smaller smart-home or hub-based deployments. It serves a different market and does not replace Seam as a purpose-built API layer for software platforms.
  • MuleSoft, Postman, or Boomi: These general integration and API tools represent a build-from-scratch path. Capterra lists general API and integration tools as alternatives, but they do not provide Seam’s purpose-built device catalog.
  • Operto, Enso Connect, and Canary Technologies: These are not direct middleware replacements. They represent the turnkey application layer that some buyers may want instead of building directly on Seam, and some use Seam behind the scenes.
  • ButterflyMX: ButterflyMX is relevant to property teams seeking video intercoms, access control, mobile and visitor access, vehicle access, cameras, package rooms, and smart lock integrations in a broader property platform.

 

Seam vs. ButterflyMX

Seam and ButterflyMX address different levels of the access technology stack. Seam supplies developer infrastructure for connecting third-party devices, while ButterflyMX supplies a property access and security platform for multifamily, commercial, gated, student housing, and other properties.

Swipe to compare →

Feature Seam ButterflyMX Why it matters
Product model Cloud API, SDK, dashboard, and component layer for third-party devices Property access and security platform that brings multiple property products together Software teams may prefer middleware, while property teams may prefer a supported platform experience
End-user and visitor access Provides APIs and components for customers or partners to build guest and resident workflows; no native consumer app Residents can receive visitor calls in the mobile app, see and speak with visitors, grant access remotely, and issue temporary visitor access The choice affects how much interface and workflow development the buyer must own
Credentials Supports device-dependent PINs, BLE or NFC mobile keys, and plastic-card encoding Supports mobile access and wallet-based credentials on compatible mobile devices Buyers should match credential types to user needs and existing entrances
Video and security scope Offers a beta API for events and clips from supported third-party cameras and integrates with selected intercom systems Offers security cameras and video intercoms within the broader access and security platform An API requires another product to present the workflow, while a platform can bring video and access together for property use
Vehicle access Depends on compatible third-party gate and intercom systems Supports vehicle access control for gates and garages as part of the broader platform Gated properties should decide between device integration and platform-level vehicle access management
Smart-lock strategy Uses a cross-brand API, with functions and connectivity varying by model Supports smart lock integrations alongside common-area access products Software builders may prioritize device breadth, while operators may prioritize how locks fit into a whole-property access system
Other property workflows Focuses on APIs for connected physical devices and customer-built applications Also includes elevator controls and package room access workflows Properties evaluating more than door access may prefer to assess the full set of workflows together

Neither model is automatically better. Seam may fit companies building a branded software product across many device manufacturers. ButterflyMX may fit property owners and operators that want mobile access, visitor workflows, video intercoms, cameras, vehicle access, and other property capabilities in one platform.

 

Frequently asked questions

 

What exactly is Seam?

Seam is a cloud API, dashboard, and SDK platform that connects customer applications to supported third-party locks, access-control systems, thermostats, sensors, and cameras. It is developer infrastructure rather than a physical lock or finished resident app.

 

How much does Seam cost?

Seam has a free entry point, followed by public plans including $10 per month for 1,000 credits, $96 for 10,000 credits, and $230 for 25,000 credits. Device and action charges consume those credits, while enterprise pricing is custom.

 

What happens to unused Seam credits?

Unused Seam credits expire at the monthly billing boundary, with a limited one-time carryover rule when upgrading. Usage above the package is billed at 1.25 times the package credit rate.

 

Which devices does Seam support?

Seam lists more than 1,000 devices across hundreds of brands, including locks, access systems, thermostats, sensors, and cameras. Check Live status, model-level actions, and connectivity for every required device.

 

Does Seam have an app for residents or guests?

No. Seam does not provide a native consumer-facing app. It supplies APIs, SDKs, webviews, and interface components that customers or partner platforms can use to build an end-user experience.

 

Does Seam require a smart-home hub?

It depends on the device. Some models connect directly, many Z-Wave or Zigbee devices require a hub, and some catalog models are local-only.

 

Is Seam SOC 2 compliant?

Yes. Seam completed a SOC 2 Type I audit performed by Johanson Group LLP.

 

Is the Seam rating on G2 for this product?

No. The G2 profile with a 4.4 out of 5 rating and eight reviews describes an unrelated sales-intelligence company, not the Seam Labs device API.

 

What are the main alternatives to Seam?

Alternatives include RemoteLock for a more managed access solution, SmartThings for smaller smart-home deployments, and general integration tools for teams building device connections from scratch. Seam-powered applications can also provide a turnkey front end without requiring buyers to use the raw API directly.

 

Is Seam a good fit?

Seam may be a good fit for software platforms and larger technical teams that want one integration layer for many device brands. Its broad catalog, developer tools, public self-serve pricing, and SOC 2 Type I compliance are meaningful strengths.

The central tradeoff is ownership. Your team must still build or obtain the end-user app, check every required device at the model level, manage deployment dependencies, and forecast credit usage.

Property teams that want a broader managed access experience should compare Seam with platforms that combine access and security workflows. ButterflyMX brings video intercoms, access control, mobile and visitor access, vehicle access, cameras, package rooms, elevator controls, and smart lock integrations into a property-focused platform.

Explore ButterflyMX to compare a property access platform with an API-first approach.

ButterflyMX deliveries

Get your free quote!

Fill in the form below, and we'll email you right back.

Want a free quote?

Fill in the form below, and we'll email you right back.

Director of Content
Katie joined the team at ButterflyMX in 2022, where she started as a Content Writer before working her way up to Director of Content. With an educational background in English and a love for SEO, Katie is passionate about writing content that educates people while being easy to digest.

Prior to joining ButterflyMX, Katie worked as a political marketing copywriter, where she wrote for political candidates and officeholders, including Federal and State Representatives, Federal and State Senators, a former Vice President, two former Speakers of the House, and several federal committees. Her work has been featured in American Camp Association, Meniscus Literary Journal, and 45th Parallel Literary Magazine.

Katie graduated from the University of Texas in 2017 and Texas State University’s Creative Writing MFA in 2020. She lives in Dallas, Texas with her dog, Ziggy, where you can catch her walking on the Katy Trail, rooting for the Longhorns during college football season, and hunting local bookstores for her next read.