A custom SMS gateway solution is a gateway configured for a specific operation: the model, SIM configuration, integration, and support matched to one workload. Custom does not necessarily mean bespoke hardware — for most operations it means choosing the right configuration from a product range and integrating it properly. The evaluation is where the value is decided: which model, which SIM count, which protocol, and which support package fit the operation.
This article is a framework for evaluating a custom SMS gateway solution, using Telarvo’s SK-SMS Gateway range as the reference. It covers the configuration decisions, the integration decisions, and the support decisions.
The Configuration Decision: Model and SIMs
The first decision is the hardware configuration. The model sets the port count, and the SIM configuration sets the number inventory. The two are chosen against different measurements: the peak sending rate sets the ports, and the volume per number sets the SIMs. A platform that peaks at 800 messages per minute and needs 200 numbers is a different configuration from one that peaks at 200 and needs 500 numbers.
Telarvo’s SK-SMS Gateway range covers the configuration space from the 4-4 to the 64-512, with eSIM versions for remote provisioning. The evaluation maps the workload to the range and picks the configuration above the measured requirement, with headroom for growth.
The Integration Decision: SMPP or HTTP
The second decision is integration. SMPP suits platforms that need delivery receipts, queue control, and precise status; HTTP API suits web and CRM tools that want simple requests. Both are supported on the same gateway, and the choice follows the platform’s architecture rather than the hardware.
The integration decision also covers the number of gateways. A single gateway serves a simple operation; a fleet serves high volume and provides redundancy. The evaluation should consider the growth path — whether the platform will outgrow one chassis and how the SMPP integration scales to multiple units.
The Support Decision: What the Operation Needs
The third decision is support. The standard package covers setup, integration, and troubleshooting, and a custom solution may also include SIM provisioning guidance, route services, and fleet configuration. The evaluation matches the support level to the operation’s technical depth: an operator with its own engineers needs less hand-holding than a business buying its first gateway.
The support decision also covers the SIM side. SIM sourcing, plan selection, and route services are part of a complete solution, and Telarvo can assemble a hardware-plus-route package. The evaluation should include the SIM plans in the total cost, since they are usually the larger recurring expense.
A Worked Evaluation Example
Walk through an evaluation. A platform sends 200,000 messages per day, peaks at 900 per minute, and serves three markets. The peak maps to a 32-port tier; the volume per number — 200,000 daily across a target of 500 per number — needs 400 SIMs, so the 32-512 configuration is the starting point. The integration is SMPP for receipts, the growth path is a second gateway, and the support package includes SIM and route guidance.
The example is an estimation framework, not a performance promise: the SIM count depends on per-number rates in each market, so the final configuration is validated with measured data. The framework shows the method — workload, integration, and support evaluated as three decisions.
When Custom Hardware Is Worth It
Most operations are served by a standard configuration from the range. Custom hardware — a modified chassis, a private-label build, or a specific firmware configuration — is worth considering for OEM programs, branded resellers, and operations with unusual physical requirements. Telarvo’s position is product-focused, so the custom discussion starts with the standard range and only moves to bespoke work when the standard configuration cannot serve the requirement.
The evaluation discipline is the same at any level: define the workload, map it to the configuration, confirm the integration, and price the total.
The Configuration Matrix
A useful way to evaluate a custom solution is a configuration matrix that maps workload profiles to models. The matrix turns the decision into a lookup rather than a negotiation:
| Workload profile | Suggested configuration | Why |
|---|---|---|
| Small operation, a few thousand messages per day | 8-8 or 8-32 | Minimal capacity, low entry cost |
| Growing platform needing number diversity | 16-128 or 16-256 | SIM density without a large chassis |
| High-volume operator, 24/7 traffic | 32-512 or 64-512 | Maximum density and headroom |
| Fleet needing remote SIM provisioning | eSIM models | Profiles managed remotely |
The matrix is a starting point, not a substitute for measurement. The decisive inputs are the peak sending rate and the per-SIM volume the operation can sustain in its markets, and those numbers come from traffic history rather than the spec sheet.
Integration Options in Detail
The SMPP and HTTP paths serve different integration styles. SMPP binds transmitter and receiver sessions, supports delivery receipts, and suits platforms that need queue control and precise status. HTTP API uses requests and callbacks, suits web and CRM tools, and is simpler to integrate for teams that already speak HTTP.
The evaluation should also cover the operations side: how the gateway is monitored, how SIMs are managed, and how delivery data flows into the platform’s reporting. A custom solution is complete when the hardware, integration, and operations fit together — not when the hardware alone is configured.
Validating the Solution Before Commitment
Before committing to a custom solution, validate the configuration with a pilot. Route a small share of live traffic through the proposed gateway, measure delivery rate, per-SIM volume, and latency, and confirm the integration behaves as designed. The pilot answers the questions the configuration matrix cannot — whether the SIMs perform on the target networks and whether the allocation settings match the workload.
Telarvo’s support team covers the pilot phase. The pilot data also feeds the final configuration, so the custom solution is validated rather than assumed.
The Economics of a Custom Solution
The cost of a custom solution has four components: hardware, SIM plans, shipping, and integration effort. The hardware price is the visible number, but the SIM plans are usually the larger recurring expense. A configuration with 256 SIMs carries 256 plan costs, and the total should be budgeted before the purchase rather than discovered after.
The integration effort is also part of the cost. SMPP integration, callback setup, and monitoring configuration take engineering time, and the evaluation should include it. For an operation with its own engineers, the effort is internal; for a business buying its first gateway, the support package covers part of it.
Telarvo Models for Custom Configurations
The SK-SMS Gateway range provides the building blocks for most custom configurations:
| Model | Ports / SIM slots | Price (USD) |
|---|---|---|
| SK-SMS Gateway 8-32 | 8 / 32 | $450.00 |
| SK-SMS Gateway 16-128 | 16 / 128 | $970.00 |
| SK-SMS Gateway 32-256 | 32 / 256 | $1,490.00 |
| SK-SMS Gateway 64-512 | 64 / 512 | $2,480.00 |
The [SMS Gateway collection](https://www.telarvostore.com/sms-gateway) lists the full range, so the evaluation can start from a real configuration space rather than a blank sheet. Most “custom” needs are met by the right standard model; the evaluation discipline is what makes the fit precise.
Operations and Monitoring for a Custom Solution
A custom solution is only as good as its operating rhythm. The daily check covers delivery rate per SIM, per-SIM volume, and failure reasons from the SMPP receipts. The weekly check covers SIM balances and inventory. The monthly check reconciles carrier invoices against the gateway’s usage records and plans the next capacity step.
The monitoring data also validates the configuration over time. If delivery rates drift, the per-SIM volume is the first place to look; if queues build during peaks, the port tier needs review. The custom solution should be reviewed quarterly against the workload, because the workload changes even when the hardware does not.
A Common Customization Mistake
The most common mistake in a custom SMS solution is customizing the wrong dimension. Teams spend the evaluation on firmware tweaks or interface details while leaving the SIM configuration undersized, and the deployment fails on delivery rather than on features. The reverse mistake is overbuilding: a 64-port solution for a workload that peaks at 200 messages per minute wastes both hardware and SIM plan costs.
The correction is to measure first and customize second. Confirm the peak rate, the per-SIM volume, and the market coverage before choosing the model; then customize the integration and support to the operation’s real shape. The configuration matrix in this article is the guard against both mistakes.
The Custom Solution Process
A custom solution moves through five stages. Requirements discovery confirms the workload — peak rate, SIM needs, markets, integration protocol, and growth plan — and produces a written specification. Configuration maps the specification to a model and SIM count, with the reasons documented. Integration covers the SMPP or HTTP setup, callbacks, and monitoring. Validation runs a pilot on a share of live traffic and confirms the numbers. Handover delivers the documentation, the configuration record, and the support path.
The process is what separates a custom solution from a box purchase. Each stage produces an artifact — a spec, a configuration record, a test report — so the solution is auditable and repeatable. For OEM or white-label programs, the process adds the brand and packaging requirements: the unit’s branding, documentation, and support handoff are defined in the same specification, and the standard Telarvo range provides the hardware base.
Frequently Asked Questions
What is a custom SMS gateway solution?
It is a gateway configuration matched to a specific workload — model, SIM count, integration, and support chosen for the operation.
Which configuration decisions matter most?
The port count (from the peak sending rate), the SIM inventory (from the volume per number), and the integration protocol (SMPP or HTTP).
Does custom mean bespoke hardware?
Not usually. Most operations are served by a standard model from the range; bespoke work is reserved for OEM programs and unusual requirements.
What support comes with a custom solution?
A 12-month warranty and 7×12 technical support, plus optional SIM provisioning, route services, and fleet configuration.
How should I evaluate the total cost?
Include the hardware, SIM plans, shipping, and any route services — the SIM plans are usually the larger recurring expense.