Summary
- 1Forma LLC's strongest public demand signal is not access-network scale. It is a Russian enterprise software proposition around BPM, low-code process design, document flow, CRM, project management, corporate communications, SaaS and on-premises deployment, backed by company marketing and registry-mirrored corporate data.
- Its RIPE footprint is real but small: RIPE records identify 1Forma LLC as a Russian LIR with AS60768, IPv4 allocation 185.80.204.0/22, IPv6 allocation 2a03:60e0::/32, and a route for the IPv4 block. RIPEstat and bgp.tools show the ASN as active with one IPv4 and one IPv6 originated prefix, and current observed connectivity concentrated around IP-Max related upstreams.
- The investment case depends on whether resource-holder control improves customer retention and contract value for software deployments. On public evidence, the resources look more like an enabling control layer than a stand-alone margin engine.
- Registry-mirrored 2025 financials show revenue growth to 391 million rubles, 109 average employees, 176 million rubles of assets, and 14.1 million rubles of profit, but profit reportedly fell sharply from 2024. That mix suggests operating leverage is uncertain even before infrastructure obligations are considered.
- The facts that would materially change the judgment are disclosed recurring software revenue, customer concentration, gross margin, renewal rates, data-center and transit costs, named hosted-service customers, and evidence that the number-resource footprint is tied to paid customer workloads rather than only internal, hosting, or resilience needs.
The Incentive Below Cloud Scale
Management's incentive is straightforward. A mid-sized software company that serves enterprise process automation cannot afford to be seen as only a feature vendor. Large customers want a system that sits near contracts, approvals, sales records, document repositories, employee communications, project workflows, and increasingly video or AI-adjacent productivity tools. That system becomes more valuable when it is hard to displace and when it fits the customer's operating constraints. In Russia, those constraints include local deployment preferences, local support, domestic software procurement habits, personal-data controls, and the practical difficulty of relying on every foreign or hyperscale cloud option in the same way buyers did before 2022.
That is the strategic reason a software company may want more infrastructure control than a pure SaaS reseller. If 1Forma can tell a large customer that its product can run in the customer's environment, in a local hosting environment, or on a controlled service stack with known network resources, the company can reduce procurement friction. The customer does not have to treat 1Forma as a loose collection of application code and consultants. It can treat the product as a managed operational layer. The higher-value revenue is still software, implementation, support, and process design. The infrastructure footprint supports the promise.
The danger is that this same footprint can seduce a company into carrying costs that bigger platforms absorb more easily. A /22 IPv4 allocation, an IPv6 /32, an autonomous system, and RIPE membership do not by themselves create cloud economics. They create obligations: registry accuracy, abuse handling, routing hygiene, upstream relationships, monitoring, failover, security work, and payment/compliance friction. A firm below cloud scale can end up paying for the control surface while the customer prices the service against cloud alternatives, local integrators, and software-only products.
The question is therefore who pays for the complexity. If customers pay a premium because 1Forma's infrastructure control makes deployments safer, more compliant, more local, or more reliable, then number-resource status can defend margin. If customers view those resources as table stakes, the cost falls back on 1Forma. The company becomes a price-taker for transit, hosting, data-center capacity, hardware, database licensing, support staff, and compliance labor, while its buyers compare it against larger software suites and cloud vendors that can spread those costs over a wider base.
Public evidence does not settle the question in 1Forma's favor. It shows a real operating company, a software product with enterprise positioning, an active routing footprint, and recent revenue growth. It does not show customer-level gross margin, recurring revenue, contract length, hosting revenue, or a disclosed link between the RIPE resources and billed customer workloads. That makes the economic reading cautious: the resource-holder footprint is useful optionality, but not yet proof of differentiated infrastructure economics.
Company Identity And Operating Boundary
1Forma LLC is best understood first as a Russian software company. Its own website presents "First Form" as a BPM and low-code platform for business-process automation. The public pages describe use cases around electronic document flow, project management, CRM, B2B2C solutions, corporate communications, knowledge bases, process design, form and interface construction, integration, and training. The site also describes SaaS and on-premises versions, a pilot-project sales motion before a first large implementation, and technical requirements for customers running the system on Linux or Windows, PostgreSQL or SQL Server, and related infrastructure.
The operating boundary matters because the assignment category is regional ISP economics, while the available public company materials do not read like those of a last-mile access provider. There is no public evidence in the reviewed sources that 1Forma sells broadband access, mass-market connectivity, IP transit, or wholesale network service as a primary line of business. The public resource records are relevant because BTW tracks number-resource governance and because those records show control over Internet number resources. They should not be inflated into a broader telecom business model without evidence.
The legal and corporate identity is also supported outside the company's own website. A public Audit-it profile, which says it uses official open sources, identifies the Russian limited liability company with OGRN 1097746017357 and INN 7704719651. It gives a Moscow address, a 26 January 2009 registration date, a main activity code for research and development in natural and technical sciences, and additional IT-related activities including consulting, data processing, hosting, and database or information-resource activity. The same profile names Denis Alekseevich Seleznev as general director since registration and lists Aleksandr Andreevich Marin and Denis Seleznev as shareholders with 51 percent and 49 percent stakes, respectively.
Those registry-mirrored details are useful but should be handled carefully. They show a company of some age and operating substance, not a newly created shell. They also show that formal activity categories are wider than the product narrative. A Russian software company may carry OKVED activities that include data processing, hosting, database services, IT consulting, and R&D without proving that each line is a meaningful revenue generator. For margin analysis, the safer conclusion is that 1Forma has a credible software and implementation boundary with adjacent infrastructure capabilities.
The RIPE identity adds a second layer. RIPE records identify organisation ORG-LA815-RIPE as 1Forma LLC, country RU, organisation type LIR, registration number 1097746017357, and maintainer references associated with FFORMA-MNT. The records show that the RIPE organisation was created in December 2014 and last modified in May 2026. The LIR designation means 1Forma sits inside the RIPE NCC membership and resource-management framework. It does not prove retail telecom service. It does prove a role in number-resource stewardship.
That split is the article's operating boundary. 1Forma is a company with public software demand signals and a modest routed resource footprint. The value question is whether those two facts reinforce each other. A buyer that needs a domestic BPM platform with controlled deployment may care that the vendor has operational competence beyond code. But unless the vendor can charge for that competence, it remains a supporting function.
Business Model: Software Revenue With Infrastructure Adjacent To It
The public business model appears to start with the "First Form" platform. The company markets a low-code BPM system with process automation, document handling, CRM, project management, corporate communication, 1F Workspace, knowledge-base functions, training, and pilot implementation. That mix points to revenue from software licenses or subscriptions, professional services, implementation projects, custom integration, maintenance, training, and potentially hosted operation for customers that choose a SaaS or managed environment.
The existence of both SaaS and on-premises positioning is important. SaaS can produce recurring revenue and centralized operating leverage if the vendor hosts many customers on shared infrastructure or a standardized managed stack. On-premises deployment can create larger implementation projects and satisfy customers that want direct control, but it often shifts some infrastructure cost to the customer and can make upgrades, support, and customization more labor-intensive. A vendor that offers both models is balancing two margin profiles: recurring platform revenue on one side, services-heavy enterprise implementation on the other.
1Forma's website leans toward enterprise process pain rather than commodity hosting. It sells the language of business control: process design, document flow, CRM, communications, training, and pilot projects before large implementation. Its technical requirements page describes serious customer-side deployment assumptions, including separate database and web servers, Linux and Windows options, PostgreSQL 16, Postgres Pro, SQL Server, reverse proxy options such as NGINX or HAProxy, .NET 8 packages, Kestrel, load balancing, SSL certificate needs, and optional video-conferencing and AI service capacity. Those details are consistent with a product that can sit inside a customer's IT estate.
This is where infrastructure may support, rather than define, the business model. A vendor serving large or regulated customers may need to show that it can operate a controlled network edge, allocate addresses, handle routing, or host isolated deployments. Number resources could help with stable service endpoints, customer segregation, migration control, test environments, disaster recovery, or avoiding dependence on a third-party address plan. But the pricing power still comes from solving workflow and integration problems. Customers do not usually pay a BPM vendor a high margin because it has an ASN; they pay because the platform becomes embedded in how work moves through the organization.
The company's client page is a self-reported demand signal. It says the system works in many companies from blue-chip customers to work groups and names brands including OBI, VkusVill, Sportmaster, Skolkovo, and VSK. Those names are meaningful as marketing signals, but they are not enough to establish contract size, renewal status, deployment scope, revenue concentration, or whether the deployments are hosted by 1Forma, installed on customer infrastructure, or implemented through partners. They show market ambition and reference value, not confirmed economics.
The pilot-project page gives a more useful clue about selling motion. Asking customers to try the BPM system before a first large implementation implies enterprise sales cycles where conversion depends on proving fit in a real environment. That can be good for retention once the product is adopted, because process platforms are sticky. It can also be expensive, because pilots, customization, training, and data migration consume skilled staff before the revenue base is fully established. Below cloud scale, the difference between a profitable pilot motion and an expensive consulting funnel is contract discipline.
The margin test is therefore not "does 1Forma have demand?" It likely has some demand. The test is whether the demand is standardized enough to scale, sticky enough to renew, and premium enough to cover infrastructure and implementation drag. Public evidence supports the first point more strongly than the second and third.
Number-Resource Evidence And What It Actually Proves
The network-resource evidence is concrete. RIPE's public database identifies AS60768 with the as-name FFORMA and organisation ORG-LA815-RIPE. It shows the autonomous system was created on 9 December 2014, assigned under RIPE, and maintained by FFORMA-MNT and RIPE-NCC-END-MNT. RIPE also shows the IPv4 allocation 185.80.204.0 to 185.80.207.255 under netname RU-1FORMA-20141210, country RU, status ALLOCATED PA, with ORG-LA815-RIPE as organisation. A corresponding route object for 185.80.204.0/22 lists origin AS60768 and describes it as a route for 1Forma LLC. RIPE also lists IPv6 allocation 2a03:60e0::/32 under netname RU-1FORMA-20141209.
RIPEstat and bgp.tools add current visibility. RIPEstat's AS overview identifies AS60768 as held by 1Forma LLC and marks it announced. Its announced-prefixes data for the late-June to early-July 2026 period shows two announced prefixes: 185.80.204.0/22 and 2a03:60e0::/32. Its ASN-neighbour data for 10 July 2026 shows two unique observed neighbours. bgp.tools, with a last update timestamp of 7 July 2026, likewise shows AS60768 active, registered to ru.1forma, originating one IPv4 and one IPv6 prefix, with four /24s of IPv4 and 65,536 /48s of IPv6 represented by the originated blocks.
That is a legitimate routing footprint, but it is not a large one. A /22 is 1,024 IPv4 addresses, enough to matter in a scarce-address market and enough for internal hosting, customer deployments, service endpoints, or small multi-tenant operations. It is not enough to imply mass-market access scale. The IPv6 /32 is large in address count, but IPv6 abundance changes the economic reading; the scarce asset is IPv4. The economic value of a /22 depends on how tightly it is tied to revenue-bearing services, whether it is cleanly routed, whether it has low-abuse reputation risk, and whether the company can use it to reduce dependency or increase customer willingness to pay.
The upstream picture reinforces the scale caution. The historical RIPE aut-num policy text lists imports and exports involving AS25091 and AS44363. RIPEstat's observed neighbours in July 2026 show AS25091 and AS58326, and bgp.tools presents AS25091 and AS58326 as upstreams associated with IP-Max SA. Public routing views can differ from historical registry policy, and relationship labels in third-party tools should be read as observations, not contracts. Still, the pattern is clear enough: 1Forma's external connectivity appears concentrated through a small set of upstream relationships rather than a broad multi-homed network with many transit and peering options.
That concentration can be perfectly rational for a software vendor. If the network exists to support controlled application delivery, internal hosting, or specific customer environments, two observed upstreams may be enough. But it limits claims about infrastructure differentiation. A company at this scale is unlikely to have the traffic volume to extract hyperscale transit economics, the peering density to reshape routing costs, or the geographic diversity to sell network performance as a stand-alone moat. The value of the footprint is operational control, not network-market power.
RIPE policy also frames the footprint as a governed resource, not free property. RIPE's IPv4 policy requires allocations and assignments to be registered in the RIPE Database, with registration data correct at all times. It states that current allocation requests are placed on a first-come, first-served waiting list, that the size of such allocation is exactly one /24, and that a single LIR can receive at most 256 IPv4 addresses under that policy path. That scarcity gives older allocations like a /22 potential strategic value, but also puts them under policy and transfer rules. The transfer policy allows legitimate holders to transfer resources, but allocated resources may only be transferred to another RIPE NCC member and scarce resources are subject to restrictions. In other words, the addresses are useful, but their value is embedded in registry governance.
The 2026 RIPE charging scheme adds a fixed-cost baseline. The annual contribution per LIR account is 1,800 euros, with listed fees for certain independent resources and ASN assignments, plus a 1,000-euro sign-up fee for new members. For a company with hundreds of millions of rubles in revenue, the direct membership fee is not large. The real cost is the staff and operational stack around resource stewardship: routing configuration, abuse response, monitoring, security, backups, DDoS readiness, supplier management, documentation, and customer support. Below cloud scale, those costs are not trivial, even if the invoice from the registry is manageable.
Revenue, Pricing, And The Margin Signal
The public financial signal is mixed. Audit-it's profile reports that in 2025 1Forma had revenue of 391 million rubles, up 70.3 million rubles, or 21.9 percent, from the prior year. It reports total assets of 176 million rubles at 31 December 2025, up 28.4 percent, net assets of 16 million rubles, and profit of 14.1 million rubles, down 76.8 percent from 2024. It also reports an average headcount of 109 employees in 2025, nine fewer than in 2024, and classifies the company as a medium enterprise.
Those figures, if accurate, make the core tension visible. Revenue growth is healthy, but profit compression is severe. A 14.1 million ruble profit on 391 million rubles of revenue implies a thin net margin in the mid-single digits before any adjustment for extraordinary items, owner compensation, tax treatment, or accounting differences. Revenue per average employee is roughly 3.6 million rubles. That may be reasonable for a Russian software and services firm, but it does not look like the clean operating leverage of a high-margin SaaS platform with very low incremental delivery cost.
The caveat is important: Audit-it is a third-party public mirror, not the company's audited management presentation, and it does not disclose gross margin, recurring revenue, backlog, cash flow, debt, or segment-level economics. But the data are still directionally useful. A company with a 21.9 percent revenue increase and a 76.8 percent profit decline is either investing heavily, absorbing cost inflation, experiencing mix shift toward lower-margin work, recognizing revenue differently, or facing project-level cost pressure. Any of those interpretations matters for a company carrying both software and infrastructure obligations.
Pricing is also opaque. 1Forma's pricing page says it offers prices for SaaS and on-premises versions, but the reviewed public materials do not supply enough standardized public pricing to model average revenue per customer. That opacity is normal in enterprise software, especially where deployments are customized. It also limits outside confidence. Without public price bands, license counts, renewal rates, implementation fees, or hosting charges, the margin case has to be inferred from product positioning and registry-mirrored financials.
The strategic issue is whether resource-holder status lets 1Forma charge more. If a customer wants a domestic BPM platform with hosted, controlled, or isolated deployment, a vendor that can manage its own address space and routing may have a credible procurement advantage. But price realization depends on how the contract is written. The company must avoid giving away infrastructure control inside a software price that was negotiated as if the customer were buying only an application. The risk is especially acute when buyers compare 1Forma against other Russian software suites, cloud-hosted collaboration platforms, or in-house deployment supported by local integrators.
Software companies can create value from infrastructure when they convert control into a measurable benefit: lower downtime, faster onboarding, better compliance evidence, stronger data location assurances, predictable endpoint management, or faster incident response. Public evidence does not show that 1Forma markets its ASN or address resources as a priced customer feature. That does not mean the resources are unused. It means outside readers should treat them as cost-bearing operational assets until revenue linkage is proven.
Cost Base And Capital Needs
The cost base has at least four layers. The first is people. A BPM and low-code platform serving enterprise customers needs developers, implementation consultants, support staff, trainers, customer-success specialists, security staff, and sales people who understand complex customer processes. The 109-employee figure is not large for the breadth of capabilities described on the website. If the company is running parallel SaaS and on-premises models, the same staff pool must support product development, custom integrations, deployment troubleshooting, documentation, training, and upgrades across different customer environments.
The second layer is product and deployment infrastructure. 1Forma's technical requirements describe a platform that can run on separate database and web servers, with Linux and Windows variants, PostgreSQL 16, Postgres Pro, SQL Server, Kestrel, IIS, NGINX or HAProxy, load balancing, SSL, mobile access requirements, optional video-conferencing capacity, GPU needs for transcription or summarization, Docker Engine, and server capacity planning. These are not incidental details. They imply that the product lives close to enterprise IT architecture and that deployment quality can affect customer confidence.
The third layer is network operations. The RIPE footprint brings address-management and routing responsibilities. The company has to maintain registry data, keep route objects coherent, handle abuse contacts, preserve reputation for its address space, manage upstream dependencies, monitor reachability, plan redundancy, and respond to failures. Even if some of that work is outsourced or handled by a hosting provider, it requires internal competence and vendor management. For a small resource holder, the human cost can matter more than the direct registry fee.
The fourth layer is capital and supplier exposure. If 1Forma hosts customer workloads itself, it needs servers, storage, backup, security tooling, data-center capacity, DDoS mitigation, transit, and support coverage. If it relies on customer-side or third-party hosting, it still needs deployment and support expertise but may lose some control. If it uses domestic cloud providers, it gets elasticity and managed services but becomes exposed to their pricing and roadmap. The company's own requirements page demonstrates that customers can deploy the product in ways that shift capital needs across 1Forma, the customer, and infrastructure providers.
This is why the "below cloud scale" question is not academic. Yandex Cloud's public pricing page advertises granular usage-based pricing and a broad list of infrastructure and network services, including compute, bare metal, object storage, CDN, load balancing, virtual private cloud, DNS, interconnect, managed PostgreSQL, managed Kubernetes, monitoring, and security tools. VK Cloud and other domestic providers similarly compete as cloud infrastructure platforms. A mid-sized application vendor can use those platforms rather than recreate them. The advantage of owning number resources must be weighed against that alternative.
Owning resources can lower switching friction and improve control, but it does not remove the need to buy or operate physical and logical infrastructure. A /22 does not provide compute, storage, power, cooling, support, DDoS filtering, or geographic redundancy. It is a scarce routing input. The economic test is whether that input creates enough customer value to cover the rest of the stack.
The reported net assets of 16 million rubles make capital discipline especially relevant. Net assets are not the same as cash, and the figure may reflect accounting choices, but it does suggest a modest balance-sheet cushion relative to 391 million rubles of revenue and the breadth of enterprise obligations. If 1Forma is trying to expand hosted services, AI-related features, video capacity, or managed deployments, it has to finance that expansion through operating cash flow, customer prepayments, partners, or external capital. Public evidence does not show which path dominates.
Suppliers And Upstream Dependency
Supplier concentration is the clearest network risk. RIPEstat's current observed neighbour data shows two unique neighbours for AS60768, and bgp.tools presents AS25091 and AS58326 as upstreams associated with IP-Max SA. The historical RIPE aut-num text includes AS25091 and AS44363, while the current observed data shows AS58326. This difference is not unusual; registry policy objects can lag real routing, and third-party tools can classify relationships differently. But the current pattern does not show a broadly diversified connectivity base.
For a software vendor, that may be sufficient. Two upstreams can provide redundancy if they are physically and commercially independent enough. But the public data suggest the dependency may not be as diversified as the count alone implies, because both current bgp.tools upstream labels point to IP-Max related connectivity. If one commercial supplier or one upstream family is central to reachability, 1Forma's bargaining power is limited. It can change suppliers, but change brings migration risk, routing work, and potential customer disruption.
Transit and hosting suppliers are only one part of the dependency map. The technical requirements point to database dependencies, operating systems, web servers, reverse proxies, .NET packages, GPU hardware for certain AI service functions, Docker, and video-conferencing capacity. Some of these are open-source or commodity layers; others involve licensing, hardware availability, or specialist administration. The company also mentions Postgres Pro and Russian Linux distributions such as Astra Linux and RED OS as supported operating environments. That support may help with domestic procurement, but every supported environment adds test, documentation, and maintenance burden.
The customer may also be a supplier of infrastructure in on-premises deployments. If the product runs inside the buyer's estate, 1Forma depends on the buyer's server quality, network configuration, certificate management, database administration, and security processes. That can reduce 1Forma's capital needs but increase support complexity. The margin risk moves from owned infrastructure to implementation labor and support calls.
This supplier structure points to a strategic choice. 1Forma can stay a software company with enough network competence to support controlled deployments, or it can move deeper into managed infrastructure. The first path likely has better margins if the product is differentiated and implementation is standardized. The second path may improve customer control but requires scale. Public evidence points more strongly to the first path than the second.
The sanctions environment adds another supplier dimension. RIPE NCC is based in the Netherlands and states in its Q2 2026 sanctions transparency report that it must comply with EU sanctions. It says that when a member or resource holder is subject to EU sanctions applicable to RIPE services, RIPE freezes registration, not use, of resources in the RIPE Database, and sanctioned parties cannot acquire more resources or transfer existing ones. It also says potential matches under investigation are treated as sanctioned until cleared, blocking new-resource or transfer requests during that period. There is no public evidence in the reviewed sources that 1Forma is sanctioned. The point is structural: Russian members face a compliance environment where documentation, payment routes, and false-positive screening can affect resource mobility and administration.
RIPE's 2026 Russian-member billing note also highlights payment administration for Russian members. Again, this is not company-specific distress. It is a reminder that even a small registry footprint is exposed to cross-border administrative friction. For a software vendor, that is one more reason not to overbuild an infrastructure story unless customers pay for the risk.
Customers, Market Dependence, And Contract Durability
The best customer signal is the company's own public client messaging. 1Forma says its system works across many companies from blue chips to work groups and names OBI, VkusVill, Sportmaster, Skolkovo, VSK, and others. It also publishes cases and presents automation use cases for large business in CRM, electronic document flow, project management, and corporate communications. The message is that 1Forma wants to be judged as an enterprise platform, not a small point solution.
Customer names, however, are not unit economics. They do not reveal whether a named organization is a current paying customer, a pilot, a limited workgroup deployment, a past implementation, a partner-led project, or a broad enterprise standard. They also do not reveal whether the revenue is recurring software subscription, on-premises license, professional service, support, training, or hosting. For a company whose public financials show profit pressure, that missing detail matters.
Contract durability in BPM can be strong. Once a system maps approvals, roles, forms, contracts, documents, and project tasks, replacement is painful. Data migration, employee retraining, custom integrations, and process redesign all raise switching costs. If 1Forma's deployments are deep inside customers' work routines, the company may have better retention than a simple collaboration tool. That would support value creation, especially if the product can expand from a pilot to multiple departments.
The opposite risk is customization drag. A BPM platform that wins because it can adapt to every customer may face low repeatability. Each customer wants its own forms, access rules, integrations, reports, security controls, hosting model, and procurement documentation. That makes the product sticky but can turn growth into a services treadmill. The reported headcount and profit decline are consistent with this risk, though not proof of it.
Market dependence is also domestic. 1Forma's public materials are Russian-language, tied to Russian enterprise deployment needs, and aligned with domestic operating-system and database options. That can be an advantage when import-substitution and local support matter. It can also limit expansion, because the product must compete in a market where budgets, procurement rules, sanctions exposure, and currency conditions are volatile. Domestic focus may protect the company from global SaaS giants in some segments, but it also reduces the pool of customers over which to spread platform and infrastructure investment.
For resource-holder economics, the crucial customer fact is whether customers require 1Forma-controlled hosting or addressing. If most customers install on their own servers, the RIPE footprint may support the company's own operations but not much customer-facing margin. If a meaningful share of customers use 1Forma-hosted services or expect controlled routing, the footprint becomes more relevant. Public evidence does not disclose the mix.
The article's cautious view follows from that gap. 1Forma has enough customer-facing software substance to make the resource footprint plausible. It does not have enough public disclosure to show that the footprint is monetized at premium margins.
Competition And Realistic Substitutes
The realistic substitutes are not only other small network operators. They are broader and more dangerous: domestic cloud infrastructure, large collaboration and CRM suites, Russian ECM and BPM platforms, customer-owned infrastructure, and integrator-built process systems. A buyer that needs process automation can choose software plus on-premises deployment, software plus cloud hosting, a larger suite, or a custom integration project. A buyer that needs hosting can use a cloud provider rather than rely on the application vendor's network footprint.
Bitrix24 is a clear reference point for suite competition. Public descriptions of Bitrix24 emphasize CRM, project management, communication, document generation, sites, business processes, time tracking, analytics, mobile access, and both cloud and on-premises options. It does not have to be identical to 1Forma to matter. It anchors buyer expectations that business-process tools come bundled with collaboration and CRM capabilities. That can pressure pricing for narrower vendors unless they are stronger in customization, local deployment, or industry-specific process depth.
Directum and ELMA-type BPM and ECM platforms create another competitive set. The Russian market has established products for electronic document management, process automation, and low-code/no-code business process design. These competitors can sell to the same departments: operations, HR, legal, finance, procurement, IT, and management. They may not share 1Forma's exact feature mix, but they compete for the same automation budget.
Cloud providers are the infrastructure substitute. Yandex Cloud publishes a broad menu of infrastructure services, including compute, bare metal, object storage, CDN, network load balancing, virtual private cloud, DNS, interconnect, managed PostgreSQL, Kubernetes, monitoring, and security tooling. VK Cloud and other domestic cloud platforms offer similar categories. For many buyers, those platforms provide more scalable infrastructure than a software vendor can build alone. If 1Forma's product can be deployed there, the cloud provider captures the infrastructure margin while 1Forma keeps software and implementation revenue.
Customer-owned infrastructure is also a substitute, and it may be the default for regulated or cautious buyers. 1Forma's own technical requirements make clear that the product can be deployed on customer servers with familiar database and operating-system choices. That keeps the vendor eligible for buyers that resist external hosting. It also means 1Forma cannot automatically monetize hosting or number resources whenever it sells software.
The competitive implication is that 1Forma's differentiation must come from process expertise, product flexibility, domestic fit, support quality, and deployment competence. Number resources can help, but they cannot carry the value proposition. In a market full of software suites and cloud capacity, a /22 and an ASN are operational assets, not a moat.
Regulatory, Geopolitical, And Operational Risk
Russia's personal-data and data-localization environment is one reason domestic deployment remains commercially important. Public legal summaries describe Federal Law No. 152-FZ as the core personal-data law and identify Russian data-localization requirements that have pushed operators to store certain personal data of Russian citizens on databases in Russia. For a workflow and CRM platform, the relevance is obvious: approvals, employee records, customer contacts, contracts, communications, and documents can all contain personal or sensitive business information. Buyers may prefer local deployment and local support even when a foreign or global cloud option exists.
This demand driver should not be overstated as a moat. Local deployment requirements can help many domestic vendors, not only 1Forma. A customer can meet local hosting needs through its own servers, a domestic cloud provider, a larger Russian software suite, or a systems integrator. 1Forma benefits only if its product and operating model solve the customer problem better than those substitutes.
Geopolitical risk cuts both ways. Domestic software vendors may gain from reduced availability or reduced attractiveness of foreign alternatives. But they also face constrained access to certain hardware, software components, payment routes, international customers, and global partner ecosystems. For a product that mentions AI service capacity, GPU needs, video-conferencing workloads, and modern database/server stacks, hardware availability and technical support can affect cost. If imported hardware becomes more expensive or harder to source, below-cloud-scale operators feel the pain earlier than large platforms with procurement leverage.
RIPE-related sanctions risk is administrative rather than product-specific. RIPE's sanctions transparency report makes clear that a sanctioned resource holder may have registration frozen and lose the ability to acquire or transfer resources, while potential matches under investigation can delay requests until cleared. The report also describes many false positives. This matters because resource mobility is part of the optional value of IPv4. If a Russian resource holder cannot easily transfer, expand, or update registration because of sanctions screening or payment problems, the economic value of the resources becomes less liquid.
Operational risk is more direct. A small routed footprint can suffer from routing mistakes, DDoS exposure, upstream outages, reputation issues, or abuse incidents. If the same addresses support customer-facing services, incidents can spill into software reputation. A company that is known primarily for BPM may not get much credit for clean network operations, but it will take blame if network issues disrupt access to business processes. That asymmetry is part of the margin risk: customers expect reliability as table stakes, while the vendor pays for it.
The route and resource records also create transparency. Customers, competitors, and researchers can observe that 1Forma originates only a small set of prefixes and relies on a limited upstream set. Transparency can support trust when records are clean and current. It can also reveal lack of scale. 1Forma cannot present itself as a broad infrastructure platform on the public routing evidence alone.
Unofficial And Market Signals
Unofficial signals should be used only as color. In this case, the market signals are relatively restrained. The company's own pages show product breadth, client-name marketing, pilot projects, technical deployment requirements, and a partner/career/contact ecosystem. bgp.tools offers an independent routing view that aligns with RIPEstat on the small number of originated prefixes and highlights current upstream labels. Audit-it mirrors registry and financial facts, including revenue, profit, employees, shareholders, and state-support entries, while stating that it uses official open sources.
None of those sources should be treated as a substitute for management disclosure. Company client pages are marketing, not audited customer schedules. Third-party routing tools are observations, not contracts. Registry mirrors can contain timing delays or errors, and financial summaries do not show segment margins. Even RIPE records prove resource registration and routing policy, not the commercial use of the resources.
The most interesting soft signal is consistency. The company's public software story and its technical requirements are consistent with a vendor that might need controlled infrastructure. The RIPE footprint is consistent with that need. The financial profile is consistent with a real mid-sized software and services company. Those pieces fit together better than a simple "paper resource holder" story would. But they still do not prove that infrastructure control is profitable.
The second soft signal is the balance between breadth and scale. 1Forma markets many capabilities: BPM, low-code design, CRM, document flow, project management, communications, knowledge base, mobile/web clients, video-related options, and AI-adjacent services. Breadth can win enterprise accounts because customers prefer fewer vendors. It can also diffuse product investment. A 109-person company supporting that breadth must choose carefully where to standardize and where to customize.
The third signal is the 2025 profit decline. If the Audit-it data are accurate, the company grew revenue but lost margin. That is not automatically negative; investment periods can precede better scale. But it raises the burden of proof. A company with shrinking profit cannot assume that resource-holder status will create value unless it can show either higher-value contracts or lower delivery cost.
What Would Change The Judgment
Several facts would make the resource-holder footprint look more valuable. The first would be disclosed recurring revenue by deployment type: SaaS hosted by 1Forma, customer-hosted on-premises licenses, partner-hosted deployments, and professional services. If the company showed that hosted recurring revenue is growing faster than services revenue and carries strong gross margin, the RIPE footprint would look more like a platform asset.
The second would be customer concentration and retention. A list of reference brands is not enough. The key data are number of paying enterprise customers, average contract value, renewal rate, expansion rate, and the share of revenue from the top five customers. A sticky BPM platform with low churn can justify infrastructure control because each retained customer pays across many years. A project-heavy vendor with concentrated revenue cannot.
The third would be cost allocation. Public accounts do not show how much 1Forma spends on data centers, transit, cloud, hardware, DDoS protection, database licensing, support, or implementation labor. If infrastructure costs are small and mostly support high-margin software, the resource-holder status is benign. If infrastructure and support costs are rising faster than revenue, it is a margin trap.
The fourth would be route and supplier resilience. Evidence of physically diverse upstreams, clear failover, multiple data-center locations, strong traffic engineering, and clean abuse reputation would support the argument that 1Forma operates its resources professionally. Evidence that the company depends on a single upstream family or one hosting environment would keep the risk discount high.
The fifth would be product standardization. Low-code vendors create value when customization happens inside repeatable product primitives rather than bespoke engineering. If 1Forma can show that pilots convert into standardized deployments with limited custom code, revenue growth can become value creation. If every customer requires unique integration and support, the company remains labor-bound.
The sixth would be proof that buyers pay for local control. Procurement documents, public case studies, or customer testimonials that identify domestic hosting, controlled deployment, or 1Forma-operated service reliability as reasons for purchase would connect the RIPE footprint to demand. Without that connection, the footprint remains an inferred support asset.
Conclusion: Useful Control, Unproven Infrastructure Margin
1Forma LLC has more substance than a bare RIPE member entry. It has a public software platform, enterprise positioning, technical deployment depth, registry-mirrored revenue and headcount, and an active number-resource footprint that has been visible since 2014. The company appears to operate at the intersection of business-process software and controlled deployment, which is a credible place for number resources to matter.
But the resource-holder evidence should be sized properly. AS60768, a /22 IPv4 allocation, and an IPv6 /32 give 1Forma operational control and scarce-address optionality. They do not create cloud scale. Current public routing observations show a small prefix set and limited upstream diversity. The company's own materials emphasize BPM, low-code automation, document flow, CRM, communications, and enterprise deployment, not transit or mass connectivity. The number resources look like an enabling layer for software and hosting flexibility, not a stand-alone profit center.
The economic conclusion is therefore cautious. 1Forma may have enough differentiated demand to make resource-holder status useful, especially for customers that value domestic deployment and operational control. Public evidence does not yet show that it earns infrastructure-like margins from that status. The safer view is that software and implementation carry the business, while the network footprint supports credibility and optionality.
That distinction matters for management. If 1Forma uses its resources to protect sticky software contracts, improve deployment trust, and support standardized hosted offerings, the footprint can add value. If it expands infrastructure responsibilities without customer-paid premium or scale, it risks becoming a price-taker: buying transit, hardware, cloud substitutes, compliance labor, and support capacity while larger platforms set buyer expectations for cost and reliability.
The fact pattern to watch is not the existence of the ASN. It is the conversion of control into recurring, high-retention, high-margin customer revenue. Until that is visible, 1Forma's resource-holder status is a strategic option with real costs attached.