Summary

  • Inmarsoft LLC has real operating evidence in the network layer: RIPE records tie it to AS202629, a small Russian routing estate, and address space that appears in Sendsay-related delivery infrastructure. That is not the same as proving it owns the customer-facing software business.
  • The public commercial boundary points upward to Internet Projects JSC, the disclosed Sendsay contracting party and software-rights holder. Inmarsoft's strongest role is therefore as a control and infrastructure company whose economics depend on how much recurring Sendsay revenue is allocated back to network operations.
  • The margin case is credible only if clean delivery, Russian data locality, API/SMTP transport, dedicated IP handling, and compliance work earn durable subscription or related-party infrastructure fees. Public 2024 revenue at Inmarsoft itself is too small to validate a standalone SaaS-growth story.
  • The reversal facts are clear: if Sendsay moves delivery away from Inmarsoft-originated space, if complaint pressure raises moderation cost, or if cheaper Russian alternatives keep capping price, the infrastructure control becomes a cost center rather than a moat.

The Invoice That Reveals The Business

Begin with the recurring invoice, because that is where the attractive version of Inmarsoft LLC would have to live. A customer using the Sendsay service pays for access to a hosted marketing and messaging platform: contacts stored, emails sent, channels added, API calls made, statistics collected, logs retained, and support requested when something breaks. That invoice looks like software. It is priced by tiers, contact bases, product families and prepayment periods.

The best version of the business has the rhythm investors like: a customer adds more contacts, sends more transactional mail, plugs in more channels, and finds that moving away would mean rebuilding templates, sender authentication, segments, data exports, webhooks, consent records and reporting.

But the invoice is not enough. In email and messaging infrastructure, the visible software fee rests on an operating surface that is less forgiving than ordinary SaaS. A marketing platform can have a good editor and still fail if mailbox providers distrust its IPs. It can have a clean pricing page and still lose money if support staff spend hours walking customers through DNS, sender registration, moderation or deliverability recovery. It can sell unlimited sends inside a contact tier and still discover that unlimited traffic is not free when mail queues, logs, storage, abuse desks and transit links have to absorb real peaks.

The control asset is not compute in the abstract. It is a bundle of address reputation, routing control, data-local infrastructure, moderation discipline and software interfaces that customers will pay for because they do not want to manage it themselves.

That is why Inmarsoft is interesting despite its small public profile. Public network sources identify AS202629 as Inmarsoft's autonomous system. The RIPE database ties the organisation object to Inmarsoft LLC, Russia, LIR status and OGRN 1147847104877. RIPEstat currently shows three IPv4 /22 prefixes and one IPv6 /29 announced by the AS. Independent network sources cross-check the same basic footprint: roughly 3,072 IPv4 addresses, a large IPv6 allocation, and a small set of observed upstream or peer relationships. DNS evidence then connects that network estate to Sendsay delivery.

The Sendsay SPF include authorizes Inmarsoft blocks, and the transactional API host resolves partly into Inmarsoft address space and partly into Internet Projects address space.

The important word is "partly." Inmarsoft is visible in the delivery system, but the public customer-facing contract is not Inmarsoft's. Sendsay legal pages identify Internet Projects JSC as the contractor and the holder of the software rights for the service. Internet Projects offers paid remote access to the Sendsay software-hardware service; Inmarsoft is the network resource holder whose domain redirects into the Sendsay public property and whose address space appears in the sending fabric. The most defensible reading is therefore a split model. Internet Projects owns the commercial product promise.

Inmarsoft controls part of the infrastructure that makes the promise possible.

That split changes the judgment. If the assignment were simply "is Inmarsoft a fast-growing SaaS company?", the public accounts would answer no. RBC Companies reports 2024 revenue of only 516,000 rubles and a net loss of 354,000 rubles, and B2B House shows a long fall from much larger reported revenue in 2019 and 2020. That statutory scale does not match the language of a major omnichannel platform. But if the question is whether Inmarsoft is an economically important infrastructure pocket inside a broader Sendsay business, the answer is more nuanced.

A small company can control valuable address space and routing policy while another related or adjacent company bills customers. The public evidence proves the network role. It does not prove the allocation of customer revenue.

Where Inmarsoft Starts And Stops

The boundary matters because it prevents two common mistakes. The first is to treat every Sendsay product claim as Inmarsoft revenue. The second is to ignore Inmarsoft because the public SaaS brand sits elsewhere. Both would be wrong. The correct boundary is narrower and more useful.

Inmarsoft's primary public evidence is legal and infrastructural. Russian business registries identify the company as active, with software-development and computing/data-processing activity codes. Its OGRN and INN match the identifiers surfaced in business profiles and in the RIPE organisation record. RIPE classifies the organisation as a local internet registry. The AS object shows import and export policy with multiple upstreams or related networks. The announced-prefix evidence shows a live routing footprint. DNS records show that Sendsay sending infrastructure authorizes Inmarsoft-held resources.

That is enough to say Inmarsoft controls part of the operating surface for a real mail and marketing platform.

Sendsay's public documents define the commercial layer differently. The offer, license agreement, user agreement, requisites page and IT-accreditation page name Internet Projects JSC as the service provider or rights holder. The service is framed as remote access to a software-hardware complex. The price pages sell newsletters, marketing automation, transport and CDP storage. The documentation describes APIs, Stream API, SMTP gateway, webhooks, security controls, moderation, personal-data compliance and account controls.

In other words, the customer buys a product; the product depends on infrastructure; the infrastructure includes Inmarsoft.

The distinction is not cosmetic. It affects revenue recognition, liability, margin and customer concentration. If a bank or retailer pays Internet Projects for Sendsay, Inmarsoft may receive no direct customer revenue. It may instead earn intercompany fees, infrastructure-service revenue, or nothing visible beyond its own statutory reporting.

If Inmarsoft owns and operates parts of the mail-delivery estate, it bears operational tasks that are not neatly reflected in the public marketing price: RPKI hygiene, route stability, PTR/DNS management, abuse mail, blocklist response, mail queue performance, transactional-host uptime, sender reputation, and capacity planning. These are not glamorous software features, but they are exactly the places where a hosted messaging business either protects margin or leaks it.

The control boundary also frames ownership risk. The public sources do not show Inmarsoft as a large independent carrier with many downstreams. They show a small AS with a compact address estate and no obvious broad access-network business. That can be a strength if the estate is specialized and clean. It can be a weakness if a few high-volume customers or a single product family dominate the use of the space. Unlike a regional access ISP, a specialized mail-transport network does not need thousands of consumer lines. It needs trust. Trust is fragile, and it often costs labor.

The Infrastructure Is A Delivery Asset, Not A Generic Cloud

Cloud competition usually invites a comparison with hyperscale compute. That would miss the point here. Inmarsoft is not publicly competing with Yandex Cloud, VK Cloud, Selectel or global hyperscalers on general-purpose virtual machines. The public evidence points to email and messaging delivery infrastructure tied to Sendsay. That is a narrower market with different economics.

The BGP footprint is small. Three IPv4 /22s equal about 3,072 IPv4 addresses, before any practical reservation, internal use, reputation segmentation or customer dedication. A single large commodity hosting company can consume more than that in one facility. But for email delivery, a few thousand well-managed addresses can matter if they are segmented across transactional streams, marketing streams, dedicated senders and internal service hosts. The limiting asset is not the raw number of addresses.

It is the reputation history attached to the addresses, the discipline of sender authentication, and the ability to keep bad traffic from contaminating good traffic.

The DNS evidence is stronger than the address count. The Sendsay SPF include authorizes Inmarsoft blocks. That means customers who include Sendsay in their own sender policies can indirectly authorize the Inmarsoft estate to send on their behalf. The transactional API host also resolves partly into Inmarsoft space. This is operational evidence, not brand copy. It shows that Inmarsoft resources are not dormant registry ornaments. They are in the path of customer-facing mail infrastructure.

Once that is established, the unit economics look more like a trust network than a server-rental business. A customer paying for newsletters or transport is buying three things at once: software to compose and segment messages, hosted systems to process and send them, and a reputational wrapper that increases the chance messages reach inboxes. In that bundle, Inmarsoft's contribution is closest to the third item. The business can charge for software access only if the network beneath it remains useful.

The problem is that trust is partly perishable. Spam complaints, high bounce rates, weak consent records, phishing attempts, scraped lists, compromised accounts and poorly configured senders can damage the shared estate. Sendsay's anti-spam agreement is therefore not a legal nicety. It is a margin-protection document. The moderation documentation is not merely customer support. It is a cost-control system. Every manual review and every blocked campaign may irritate a customer, but every under-reviewed bad campaign can harm the entire sending base.

Inmarsoft's infrastructure only has recurring value if the commercial platform can reject bad volume without losing too much good revenue.

Pricing Shows A Real Subscription Ambition

Sendsay's public price architecture is subscription-shaped. Newsletter tiers rise with contact-base size. Marketing tiers charge more for broader automation and CDP functionality. Discounts reward three, six and twelve-month prepayment. The service notes that platform access is generally not subject to VAT while add-ons such as personal managers, dedicated IP addresses and SMS are treated separately. That is a software-margin structure, not a one-off development shop.

The price book also reveals the ceiling. For small and mid-sized accounts, Russian competitors publish alternatives that are visibly cheaper or differently packaged. Unisender sells entry-level email plans and a separate transport product. DashaMail comparisons show lower prices at several contact tiers. RuSender advertises free and paid plans with email API/SMTP options. The market is not empty. A customer that only needs basic email can shop aggressively.

A customer that needs CDP, multichannel segmentation, Russian data locality, API, logs, compliance controls and deliverability support has fewer direct substitutes, but still has alternatives.

This is where Inmarsoft's control asset must earn its keep. If Sendsay were just another newsletter editor, its price would be capped by cheaper email-service providers. If it offers dependable Russian-hosted transport with authenticated sending, data locality, logs, dedicated IP options, security controls and a route around foreign SaaS withdrawal, it can defend a higher price. Inmarsoft's address and routing role supports that higher-value proposition. It makes the service more than a web interface.

Still, the subscription ambition has a hidden cost. The price pages include unlimited sends in some contact tiers. "Unlimited" in marketing copy does not mean unlimited cost. It means the provider believes average usage and abuse controls will keep traffic inside profitable bounds. Heavy senders, seasonal peaks and transactional loads can invert that assumption. The Transport documentation acknowledges individualized settings and rate-limit behavior. The Stream API documentation discusses high-throughput use, batching, retries, failover and the operational distinction between mass and transactional traffic.

That is exactly where a hosted platform leaves pure software and becomes infrastructure.

The attractive economics come from spreading fixed platform and reputation work across many accounts. The unattractive economics come from the outliers: customers with poor lists, complex integrations, aggressive peak sends, weak consent history, demanding deliverability needs or dedicated-IP requirements. Those accounts may pay more, but they also consume the scarce labor that determines whether the address estate remains clean.

The Custom Labor Trap

The danger in this model is that the invoice says subscription while the work behaves like services. A customer sees a monthly tariff. The provider sees a moving queue of technical requests: authenticate a sending domain, warm up a dedicated address, explain why a transactional message was delayed, review a rejected list import, register an SMS sender name, export logs for an internal audit, connect a webhook to a retail CRM, separate transactional traffic from promotional traffic, diagnose a spike in bounces, or prove to a security department that data handling fits Russian personal-data requirements. Each request may be normal.

Together they decide whether software margin survives.

Sendsay's own documentation implies this burden. Stream API access is not framed as a frictionless commodity switch for every account; some settings require contacting support. SMTP gateway access also runs through support or a manager. SMS connection has contract and operator deadlines. Moderation can put campaigns into manual review. Dedicated IPs are offered as a way to protect deliverability, but dedicated IPs require care: warm-up, traffic separation, sender discipline, reverse DNS, monitoring and sometimes unpleasant conversations with customers whose lists are damaging reputation.

These are not one-time tasks if the platform serves businesses with changing campaigns and seasonal peaks.

This is the point at which Inmarsoft's infrastructure role either becomes valuable or becomes trapped. If the platform can codify most of the work into self-service controls, clear rate limits, automated moderation, reusable onboarding and priced add-ons, then the network estate supports recurring margin. Customers pay for trust, and the provider delivers it through a repeatable machine. If the platform needs human intervention for each serious customer, then the recurring invoice partly disguises a consulting shop. Inmarsoft's address control still matters, but it does not automatically create high margin.

The tariff structure gives both possibilities. Contact-tier pricing and annual discounts encourage retention and prepaid cash. The product pages advertise several levels of capability, from basic newsletters to marketing automation and transport. That allows segmentation: low-touch accounts can stay on simple plans, while higher-value users pay for CDP, transport, logs, enhanced security or personal service. Yet a wide product surface also creates more edge cases. Email, web push, mobile push, SMS, Telegram, VK, API, SMTP, webhooks, logs and segmentation are not one product in operational terms. They are many failure modes under one brand.

The best margin defense is therefore not raw price increases. It is customer selection. Inmarsoft-linked infrastructure is most valuable for customers who need controlled Russian-hosted messaging, not for customers who merely want the cheapest way to send a coupon blast. The wrong customers create complaint cost, list-hygiene cost and support cost. The right customers pay for resilience, compliance, statistics and control. A delivery platform can survive some noisy small accounts, but its economics improve when high-volume traffic comes from organizations with disciplined consent records and predictable operational teams.

There is also a capital discipline point. In ordinary cloud hosting, adding capacity often means buying servers, storage and network ports ahead of demand. In email delivery, capital is partly reputational. A provider cannot instantly create clean sending history by buying a block of addresses. It must earn reputation gradually, segment traffic and avoid allowing one sender to burn a pool used by another. This turns time into capital. Inmarsoft's existing resources have value because they already sit inside the service's authentication and routing pattern.

But that value can be destroyed faster than it can be rebuilt if abuse control fails.

That is why the public complaint signals matter even when they are small. One AbuseIPDB report at zero percent confidence is not a business thesis. A Spam.org complaint is not a verdict. But each is a reminder that the infrastructure is exposed to recipient reaction. The cost of one bad campaign is not just the bandwidth for that campaign. It is the support time, the moderation review, the possible blocklist work, the risk to neighboring senders and the future customer who asks why deliverability dipped.

The custom labor trap also explains why the visible public accounts for Inmarsoft cannot be ignored. A company with a small team and low statutory revenue may still hold important resources, but it cannot absorb unlimited operational load unless another entity funds the staff. If the broader Sendsay business finances engineering and support through Internet Projects, Inmarsoft can remain a lean infrastructure holder. If Inmarsoft itself is expected to perform the heavy operational work, the 2024 revenue figure looks inadequate.

Either way, the conclusion is the same: the margin is group-level and operational, not automatic in the Inmarsoft ledger.

Public Accounts Warn Against A Simple Growth Story

The public financial data for Inmarsoft itself is the biggest reason for caution. RBC Companies and B2B House show a micro-scale 2024 business, with revenue of 516,000 rubles and a net loss of 354,000 rubles. B2B House's time series shows revenue above 56 million rubles in 2018, above 60 million rubles in 2019 and 2020, and then a sharp fall by 2022. The exact internal reason is not public in the sources reviewed. It could reflect restructuring, revenue moved to another entity, changed contracts, changed accounting scope, loss of business, or a narrower infrastructure role.

That uncertainty matters. If Inmarsoft once booked more substantial Sendsay-related or software-development revenue and no longer does, the standalone entity may be economically peripheral even while its network assets remain technically important. If the fall reflects internal reallocation to Internet Projects JSC, the public Inmarsoft accounts understate the economics of the infrastructure estate. If the fall reflects actual customer or product decline, the network role may be a remnant rather than a moat.

The article's judgment therefore cannot treat Inmarsoft's statutory revenue as proof of the Sendsay platform's total scale. It also cannot ignore the revenue. A company that controls an AS and appears in delivery infrastructure can still be a low-revenue support vehicle. That is the most likely reading unless private contracts say otherwise. The public data support "infrastructure control point," not "large independent cloud provider."

The upside case requires an intercompany view. If Internet Projects sells subscriptions and pays Inmarsoft for dedicated delivery, network operations, LIR administration, infrastructure engineering or address reputation management, Inmarsoft may have durable related-party economics that do not look like ordinary market sales. That can be stable, but it is also concentrated. A single group-level product decision could change the economics quickly.

The downside case is simpler. If Inmarsoft is mostly a historical legal shell around IP resources, with limited revenue and low headcount, the software-margin upside belongs elsewhere. In that case, the correct valuation of Inmarsoft is not the multiple of a SaaS company but the utility value of a controlled address estate and the operational effort attached to it.

Suppliers, Upstreams And Concentration

AS202629's public upstream and peer picture is compact. Sources consistently mention RETN and Severen-Telecom, with EdgeCenter, Internet Projects and RetnNet appearing in some views or registry policy. A small AS can operate well with a limited upstream set, especially for a specialized mail platform, but it has less room for supplier trouble than a larger carrier. Routing diversity is not only about uptime. It is about latency to major mail providers, resilience during filtering events, and flexibility if one upstream relationship becomes commercially or politically awkward.

Supplier concentration also extends beyond transit. A messaging platform depends on data-center space, servers, storage, DNS, TLS certificates, SMS aggregators or mobile operators, payment and document-flow systems, anti-abuse tooling, support staff, and software engineers. Sendsay's public documents speak about Russian office and servers, ruble pricing, security attestations, GOST VPN options, role-based access controls and dedicated IPs. Those features help win domestic trust, especially from banks, insurers, government-adjacent customers and companies that worry about foreign SaaS continuity.

They also bind the cost base to Russian infrastructure and compliance conditions.

SMS is a clear example. Sendsay documentation says SMS is an additional option for paid legal-entity accounts and requires registration steps and deadlines with operators. That is not a pure software toggle. It is a supplier and compliance process. API sending is similar. A customer can technically integrate through API, Stream API or SMTP gateway, but support may still need to approve, configure, troubleshoot and explain the edge cases. The more Sendsay sells itself as safe enterprise infrastructure, the more of this labor it must absorb.

The best version of Inmarsoft's role is to make this supplier mesh more controllable. Owning or administering address resources gives the group more autonomy than reselling a foreign email platform. It can set SPF, DKIM, reverse DNS, routing policy, dedicated IP pools and traffic segmentation directly. The worst version is that control only increases responsibility. If customers complain about deliverability or regulators ask about data handling, owning the infrastructure means there is nowhere to pass the issue.

Customer Concentration And Switching Costs

The public sources do not disclose a customer concentration table. Sendsay marketing pages refer to trust from retail, small business, banks and government services, and public SPF lookups for several Russian domains show the Sendsay SPF include in use. That is enough to infer real production use. It is not enough to know whether revenue is spread across thousands of small accounts or concentrated in a small number of large customers.

The economic implications differ sharply. A broad base of small and mid-sized customers supports classic SaaS margin if onboarding is self-service and support is contained. But email marketing often produces many support tickets: imports, sender authentication, moderation, list hygiene, blocked domains, template rendering, billing documents, personal-data questions and complaints from recipients. A few large customers can justify personal service and dedicated infrastructure, but they also create concentration risk and custom work. The public documents allow both models.

Switching costs are real but uneven. A simple newsletter sender with a small contact list can migrate to Unisender, DashaMail, RuSender or another tool. A customer using Sendsay as a CDP-like store with segmentation, automated scenarios, event webhooks, transactional API, logs, multiple channels and personal-data documentation has more to unwind. The more operational history stored in Sendsay, the stickier it becomes. The more a customer uses only basic mass email, the more price-sensitive it becomes.

That difference should shape Inmarsoft's margin strategy. The infrastructure estate should not chase every low-margin sender. It should support customers whose need for data locality, deliverability, logs, API reliability and compliance justifies a higher platform fee. When the platform sells to customers that could run simple campaigns elsewhere, Inmarsoft's controlled address space becomes a shared utility exposed to the weakest list hygiene in the customer base.

Customer trust signals are mixed. G2 shows only one visible review, positive but too thin to carry much weight. Otzovik shows a low rating and complaints about spam, interface complexity and support response. A recent review article describes Sendsay as a heavy platform with powerful features but also moderation, support and import complaints. These are unofficial signals, not audited facts. They do, however, point in the same direction as the unit-economics analysis: support, moderation and reputation management are not side issues. They are the cost centers that determine whether recurring invoices turn into margin.

Reputation Is A Variable Cost

Email infrastructure has a nasty feature: bad customers can spend other customers' reputation. A shared sending platform must police consent, bounces, complaint rates, misleading content and compromised accounts. Sendsay's anti-spam policy is unusually central to the economics because the IP estate is limited and visible. The policy defines spam incidents, imposes consent obligations, restricts bought or scraped lists, sets complaint and invalid-address thresholds, and bars or restricts risky categories. This is not just compliance language. It is infrastructure maintenance.

Public abuse traces should be handled carefully. Spam.org shows a complaint involving a Sendsay return path and an Inmarsoft-controlled IP. AbuseIPDB shows an Inmarsoft IP with one historical report and zero percent confidence. Those records do not prove systemic abuse. A large legitimate email platform will almost inevitably appear in complaint datasets because customers send mail, recipients complain, and some senders behave poorly. The useful conclusion is narrower: complaint pressure exists, and the platform has to fund the people and systems that keep it from becoming existential.

Moderation is therefore a margin lever and a customer-friction point. Sendsay documentation says campaigns can go to manual moderation when automatic checks flag risk or when accounts are new. Customers dislike waiting. Review sites reflect that. But moderation protects the network. If Inmarsoft-originated addresses become associated with uncontrolled senders, the cost shows up in deliverability, support and possibly lost customers. If moderation is too strict or slow, the cost shows up in churn and negative reviews. The profitable point is hard to hit.

The SPF evidence also cuts both ways. It shows that Inmarsoft resources are trusted enough to be authorized for Sendsay-related sending. It also means that any deliverability issue on those resources can affect the Sendsay promise. The more deeply Inmarsoft sits inside customer mail authentication, the more important its operational hygiene becomes.

Regulation And Geopolitics Are A Sales Advantage Until They Become A Constraint

The Russian regulatory environment creates demand for domestic SaaS. Sendsay's own pages stress Russian servers, Russian legal entity, ruble prices, personal-data compliance and entry in the Russian software registry. Those claims matter after foreign SaaS exits or service restrictions. A company that cannot risk losing access to a foreign marketing platform may prefer a domestic provider even if the interface is less polished or the price is not the lowest.

For Inmarsoft, this is the best strategic case. The network estate supports a domestic platform that can promise data locality and operational continuity. The customer does not need to assemble its own mail servers, address reputation, logs, consent mechanisms, webhooks, API sending, SMS registration and compliance documentation. It buys a Russian-hosted service and shifts the technical burden to the provider.

But regulation is also a cost. Personal-data law requires documentation, controls and evidence. Anti-spam rules and advertising law expectations require consent discipline. SMS and messenger channels add operator and platform rules. Russian software-registry positioning may help sales, but it also keeps the product under a domestic regulatory spotlight. Security claims create obligations. The more Sendsay sells to banks, insurers and government-adjacent services, the more demanding the audits become.

Geopolitics narrows options. Russian localization and ruble pricing are helpful for domestic customers, but they make expansion to some foreign buyers harder. International providers may be unavailable or unattractive to Russian clients, yet domestic infrastructure can also face sanctions, equipment, payment, certificate, software-supply and cross-border trust issues. A small AS with domestic dependencies is not insulated from those pressures. It is specialized inside them.

This is why the phrase "cloud competition" should be read carefully. Inmarsoft is not beating public cloud on scale. It is participating in a domestic-control argument: a Russian service, with Russian data handling, routed through domestic and regional networks, serving customers who value continuity and compliance more than a global cloud brand. That argument can support recurring revenue, but only if the product quality stays close enough to alternatives.

What Would Change The Judgment

Several facts would materially improve the case for Inmarsoft. The first would be disclosure that it receives recurring infrastructure revenue from the Sendsay platform, dedicated IP services, transport operations or related software hosting. The second would be evidence that Sendsay's highest-value enterprise customers depend specifically on Inmarsoft-originated delivery resources. The third would be continued growth in Inmarsoft-address authorization across customer SPF records without a corresponding rise in complaint and blocklist signals. The fourth would be a rebound in statutory revenue after the post-2021 decline.

Several facts would weaken the case. If the Sendsay platform migrates transactional hosts and SPF authorization away from Inmarsoft space, Inmarsoft's role becomes historical. If RIPE resources are transferred or the AS stops announcing the current prefixes, the control asset disappears. If cheaper competitors keep moving upmarket into CDP, API transport and compliance features, Sendsay's price premium narrows. If review and complaint signals worsen, moderation and support costs rise.

If Internet Projects captures nearly all customer economics while Inmarsoft remains a micro-revenue infrastructure holder, the software-margin thesis belongs to the wrong legal entity.

There is also a middle path, which is probably closest to the public evidence. Inmarsoft may not need to be a large standalone company to matter. It may be a specialized operating company whose address resources, LIR status, routing policy and technical staff support the broader Sendsay product. In that role, its economic value is not visible in retail branding. It is visible when mail keeps moving, when customers authorize the platform in SPF records, when transactional API hosts answer from controlled space, and when abuse pressure stays manageable.

That makes the company strategically important but financially opaque. The article's title says Inmarsoft must turn hosting control into recurring software margin. The sharper conclusion is that it can only do so indirectly unless the revenue boundary changes. The control is real. The public software contract sits elsewhere. The margin is available to the group if the infrastructure lowers churn, supports higher tiers, protects deliverability and anchors Russian compliance. It is not yet proven inside Inmarsoft's own public accounts.

Evidence Register

The public evidence base falls into five groups. First are registry and finance records. RBC Companies, T-Bank, B2B House and CIO Navigator identify Inmarsoft as an active Saint Petersburg software and IT company, with OGRN 1147847104877, INN 7813584891, microenterprise indicators, ownership and management data, and a weak 2024 financial result. These sources are consistent on identity, while the financial trend requires caution because registry aggregators can lag or differ in detail.

Second are network records. RIPE's member page, RIPE database objects and RIPEstat announced-prefix data connect Inmarsoft to AS202629 and its live routing estate. IPinfo, Hurricane Electric BGP, Cloudflare Radar, IP2Location and IPGeolocation independently corroborate the same AS identity, approximate address estate and peer or upstream picture. These sources support the claim that Inmarsoft controls real internet resources, not merely a dormant company name.

Third are DNS and delivery records. Google Public DNS queries show that the Sendsay SPF include authorizes Inmarsoft IPv4 and IPv6 blocks, that the Sendsay root SPF includes that mechanism, and that the transactional API host resolves partly into Inmarsoft space. This is the strongest operating link between Inmarsoft and the Sendsay platform because it comes from live DNS behavior rather than promotional copy.

Fourth are primary Sendsay commercial and product documents. The requisites page, IT-accreditation page, public offer, license agreement, user agreement, price pages, transport documentation, Stream API documentation, SMTP gateway documentation, webhook documentation, security pages, moderation page and 2025 product update show the product model, the contract boundary, the remote-access licensing structure, the compliance claims, the API and SMTP operating surface, and the support and moderation burden. They also show that Internet Projects JSC, not Inmarsoft, is the visible customer-contract party.

Fifth are market and unofficial signals. Competitor price pages from Unisender, Unisender Go, DashaMail and RuSender show the alternatives that cap price. G2 and Otzovik show thin but useful review signals. Spam.org and AbuseIPDB show public complaint traces that should not be overread, but which confirm that reputation management is an active risk in this sector. Together, these sources support a cautious judgment: Inmarsoft's infrastructure is real, its margin relevance is plausible, and its standalone software-revenue story remains unproven.

Sources