SignalWire review

SignalWire is a programmable communications platform for developers building voice, video, messaging and AI into their own applications. Rather than a fixed phone system, it lets teams define call flows and AI agents in code; the platform manages call state and coordination. Call routing can use what a caller says, caller information or answering-machine detection. Developers can write flows in SWML, a JSON or YAML format, use REST APIs to send SMS, place calls and provision numbers, and use realtime SDKs over WebSocket to respond to call events. SignalWire groups those functions under one programmable control layer rather than requiring separate products for each channel. It is aimed at teams comfortable building and maintaining communication logic themselves. Pricing is usage-based, with per-minute, per-message and monthly number fees; the pricing page does not publish subscription-plan pricing or annual billing.

SignalWire’s strongest case is breadth for teams that want to build communications into software. Voice, video, messaging and AI sit behind one programmable layer, while SWML flows let developers define how those channels behave in JSON or YAML. That gives teams a way to coordinate a custom call experience instead of being limited to a preset call menu.

• Call routing can respond to spoken requests, caller information or answering-machine detection.
• Code-directed AI agents can follow defined conversation steps and use tools.
• REST APIs cover tasks such as sending SMS, placing calls and provisioning numbers; realtime SDKs let applications react to call events over WebSocket.
• Usage pricing is itemized by service. For example, the pricing page lists local SMS at $0.00415 per segment inbound and outbound, and local numbers at $0.50/month.

That model can suit a team that needs specific call logic or wants to add communications to an existing product. One Reddit user described using SignalWire while exploring a tailored group-texting tool, though the thread does not establish how well the service worked at scale. The broader point is that SignalWire exposes building blocks, not a turnkey messaging community.

Costs are split across usage, number rental and add-ons, so there is no simple subscription price to compare with a flat-plan service. The pricing page lists AI Agent Runtime at $0.16/min, with voice transport billed separately; its typical standard SIP/PSTN total is about $0.163–$0.168/min. Local PSTN is $0.0066/min inbound and $0.008/min outbound. Those rates can add up with traffic, and carrier fees may apply to messages. The page does not publish annual billing or subscription-plan pricing; it lists no free plan, and a free-trial offer is not published.

Some extras have meaningful costs or conditions. High-throughput calling above 1 call/sec starts at $15/month per tier, and the listed tiers reach $40/month for 201–250 calls/sec, with a three-month commitment. SMS short codes cost $1,500 or $3,000 per quarter plus $750 setup; vanity codes require at least $500 monthly spend. Campaign fees range from $0 to $30/month, plus a $4.50 one-time brand registration fee. The page also lists a $250 T-Mobile inactivity passthrough fee after 60 inactive days. A Reddit commenter complained about cost and said both call legs were billed; treat that as one user’s account, not a universal rate rule.

SignalWire has no published subscription-plan price or annual billing. The pricing page lists usage charges instead, so costs rise with minutes, messages, numbers and add-ons; there is no flat-plan tier jump to compare. AI Agent Runtime is $0.16/min, with standard TTS included but voice transport billed separately. The page estimates a typical standard SIP/PSTN total of about $0.163–$0.168/min.

Voice API rates include SIP/WebRTC at $0.003/min and local PSTN at $0.0066 inbound or $0.008 outbound. Local SMS is $0.00415 per segment, inbound or outbound. Local numbers cost $0.50/month; toll-free numbers cost $0.80/month. Add-ons can change the bill: recording is $0.002/min, transcription is $0.02 per 15 seconds, and conferencing is $0.0018/min per participant. WhatsApp is $0.005/message plus Meta fees, and carrier fees may also apply. The pricing page lists a $250 T-Mobile inactivity passthrough fee after 60 inactive days. We’d model expected traffic and extras before comparing costs.

Switching effort depends on how much of your communications logic lives in SignalWire. The product material describes call flows in SWML JSON or YAML, REST APIs, and realtime control over WebSocket. If your app uses those flows and APIs, moving means replacing or rebuilding the integrations that rely on them; a simple number transfer alone would not cover that work. That is an architectural inference, not a documented migration estimate.

The published material does not say what data export tools are available, how number porting is handled during migration, or whether SignalWire offers migration assistance. Confirm those details before committing, especially if you need call history, recordings, or message records elsewhere. We also don’t have Reddit posts or comments in the published material, so we can’t credibly say what users report as reasons for leaving. The clearest switching risk supported here is usage-based billing: teams that need predictable all-in costs may prefer a provider with published flat pricing.