The Story Behind
SWSS Chain
From a payments infrastructure company in 2019 to a globally registered engineering organisation, building the Layer 1 where real world value settles with verifiable on chain proof.
Our Mission
To build the settlement layer real world assets actually require, together with the identity, custody and compliance infrastructure that makes settlement provable rather than asserted.
An Engineering Company Before A Chain
SWSS began in 2019 as a payments and fintech infrastructure company. The problem that shaped everything since was a settlement problem: value that exists in the real world, whether a property, an invoice, a booking or an identity, moves through systems that cannot prove to each other what happened, and reconciliation becomes a business in its own right.
Our answer was not another application on someone else's chain. It was to build the settlement layer itself, together with the identity, custody and compliance infrastructure a regulated asset actually requires. SWSS Chain is a purpose-built Layer 1 for real world asset settlement; the products around it exist because settlement is useless without them.
The company is registered across four jurisdictions and operates as a single engineering organisation. What we publish is measured from the running networks rather than transcribed, which is why the numbers on this site can be checked against the chain instead of taken on trust.
None of that began with a chain. SWSS is a technology and financial infrastructure group whose business is enterprise engineering across six practices, and the network is the output of one of them. The order matters: the protocol was funded by the engineering business, not the other way round, and the business still runs.
- Legal name
- SWSS Fintech
- Operating since
- 2019
- Parent entity
- British Virgin Islands
- Registered in
- BVI, Canada, United Kingdom, Malaysia
- Engineering
- Six divisions, one release process
- Products
- 17 across the ecosystem
- Network
- SWSS Chain, a purpose built Layer 1
Six Practices, One Engineering Standard
Most of what SWSS builds is never seen by the people who depend on it. It is the settlement, identity, security and infrastructure underneath a system somebody else puts their name on. That work is delivered through six practices, and they share one architecture review, one security standard and one release process.
Enterprise AI & Machine Learning
Applied artificial intelligence delivered into production systems rather than into pilots: custom models, enterprise language systems, predictive analytics and computer vision, built to run against a client's own data under their own governance.
Cybersecurity & Digital Defence
Defensive engineering for organisations whose exposure is measured in regulatory consequence: continuous threat monitoring, security operations, identity and access management, and the hardening work that keeps an estate defensible after the project ends.
Blockchain & Decentralised Systems
Distributed ledger engineering for enterprises, from private settlement networks to the public infrastructure the group operates itself. This is the division whose own long-running programme became SWSS Chain.
Cloud Engineering & Platform
Multi-cloud architecture, infrastructure as code and delivery automation. The group runs its own public networks on this practice, so what is sold to clients is the same discipline that carries production traffic internally.
Smart Infrastructure & Automation
The physical layer: building management, industrial IoT, sensor networks and the real-time monitoring that turns a building or a plant into an instrumented asset with data a financial system can act on.
Payments & Banking Infrastructure
Payment gateway engineering and core banking modernisation, operated out of the group's registered payments entity. It is the division where regulated money movement and distributed settlement meet in the same system.
The Operating Model, Stated Plainly
How a company works is usually invisible to the people buying from it. Ours is written down here because it is the reason the rest of this site can be checked rather than believed.
One Organisation, Four Registrations
The offices are jurisdictions, not silos. A single engineering organisation spans all four, so a client in London is served by the same teams, standards and review process as a client anywhere else. Local counsel is retained in each so counterparties always contract with an advised entity.
One Release Process
Every property the group operates, from the protocol to the public sites, ships through the same gated pipeline. A release that fails an automated check does not ship, and nobody's seniority overrides that. The gate is the point: it is the part of the process that does not get tired or busy.
Published Figures Are Measured
Versions, block times and counts are read from the running networks on a schedule and published from one source that every SWSS property consumes. The practice exists because a published version once sat five releases behind the chain for fifty four days while every property quoted it.
Authorities Are Separated
Identity, custody, asset records and validator operations are owned by different systems with different codebases. No single component can both establish who a party is and move what they hold, which is a structural protection rather than a procedural one.
How Anything Ships
Specified
Written down before it is built, against the standard it has to meet.
Reviewed
Architecture and security review by people who did not write it.
Gated
Automated checks that block the release rather than warn about it.
Released
Staged deploy, then the published facts resync from the live network.
Key Milestones
From the founding vision to a Layer 1 in production testing, every step has been guided by the same settlement problem.
Foundation & Vision
SWSS founded to bridge traditional enterprises with digital infrastructure. Initial focus on payment gateways and fintech systems.
The first systems were payment gateways and back office integrations for businesses whose money moved faster than their records did. That gap, between a transaction happening and everyone agreeing it happened, is the problem the company has worked on ever since.
Technology Foundation
Core development teams established for AI, blockchain and cybersecurity, and the first enterprise-grade platforms built.
Delivery stopped being project shaped and became practice shaped: standing teams, a shared stack and review by people who had not written the code. It is the year the engineering discipline the group still runs on was set.
Innovation Expansion
Dedicated divisions launched for smart infrastructure and IoT, with proprietary algorithms for predictive analytics and automation.
Smart infrastructure brought the physical world into scope, from building management to sensor networks, and with it the question of how a building's data could ever be trusted by a financial system that did not own the sensors.
Strategic Growth
Engineering portfolio expanded into cloud architecture, with partnerships built alongside technology leaders worldwide.
Cloud architecture became a division rather than a skill, which is what allowed the group to operate what it builds rather than handing it over. Everything SWSS runs in production today sits on that practice.
Market Expansion
Diversified across healthcare, manufacturing, energy and government, and deepened enterprise security capability.
Healthcare, manufacturing, energy and government each arrived with their own regulator and their own definition of acceptable downtime, and the security capability deepened to meet them.
Global Registration
Officially registered across the British Virgin Islands, Canada, the United Kingdom and Malaysia, establishing an international operational framework.
Registration across four jurisdictions gave the group a structure that counterparties can contract with: a parent holding the intellectual property, a licensed payments entity, a European commercial office and an engineering centre.
Engineering The Settlement Layer
Seven years of engineering practice consolidated into a purpose-built Layer 1 for real world asset settlement, and the product ecosystem that runs on it.
The settlement problem defined in 2019 became a purpose built Layer 1, with the identity, custody and deed infrastructure a regulated asset actually requires built alongside it rather than after it.
Registered Worldwide
Two legal entities carry the four offices. SWSS Foundation holds the parent in the British Virgin Islands and the engineering centre in Malaysia; SWSS Fintech holds the licensed payments entity in Canada and commercial operations in the United Kingdom. The engineering centre in Malaysia has operated since 2019, and in 2024 SWSS completed registration across four international jurisdictions, establishing a structure in which each office carries a defined mandate and counterparties in every region contract with a locally registered, locally advised entity. The offices are jurisdictions rather than silos: one engineering organisation spans all four, under one set of standards.
British Virgin Islands
SWSS Foundation
International HQ
Parent company and owner of the group's intellectual property. Group governance, treasury policy and material agreements sit here.
Canada
SWSS Fintech
North America Operations
Holds the Money Services Business registration covering virtual currency, payment services and foreign exchange.
United Kingdom
SWSS Fintech
European Operations
Commercial operations for the United Kingdom and Europe, institutional relationships and local counsel.
Malaysia
SWSS Foundation
Asia Pacific Centre
The group's principal engineering and research centre, where most of the technical headcount sits.
Global Operations
Two entities, four registrations
A Technology Group That Happens To Run A Layer 1
It would be easy to read this page and conclude that SWSS is a blockchain company with a long preamble. The order is the other way round. SWSS Fintech is a technology and financial infrastructure group, and SWSS Chain is the settlement layer one of its practices built because no existing network did what the group's own clients needed.
That distinction matters when you are deciding whether to depend on any of this. A network owned by a company with 17 products and an enterprise business behind it has a different failure mode from a network that is the whole of its sponsor's existence.
The Company Is Older Than The Chain
SWSS was delivering payment and enterprise systems years before any of it settled on a ledger, and that business still runs. The protocol was funded out of engineering revenue rather than out of a sale.
The Chain Is One Programme
SWSS Chain is what the blockchain and decentralised systems practice built. It is the largest single programme in the group and one of six practices, so judging the company by the network alone measures a part and calls it the whole.
The Group Is Its Own First User
Identity, custody, asset records and validator operations are SWSS products settling on the SWSS network. The chain carries real dependencies from day one instead of waiting for somebody else to build on it.
What Drives Us
Six values, each with an example of it actually being applied. A value without one is a poster, and this company has enough engineering behind it to show its working.
Innovation First
We explore emerging technology in order to deliver engineering that stays ahead of the curve rather than catching up to it, and we would rather build the missing layer than work around its absence.
In practice. No existing network settled real world deeds the way our clients needed, so we built the Layer 1 and the deed standard instead of adapting a contract to pretend.
Partnership
We work as an extension of the teams we build with, understanding the problem before proposing the system, and staying with it after the launch when the real behaviour shows up.
In practice. Delivery teams are standing teams rather than assembled ones, so the people who designed a system are the people who answer for it a year later.
Integrity & Trust
We operate with transparency and accountability. On chain that means every claim is independently verifiable rather than asserted, and where our pages and the network disagree, the network is right.
In practice. Protocol versions on this site are read from the running networks every hour. The practice exists because a published version once sat five releases behind the chain for fifty four days.
Excellence
We pursue the highest standard in everything we ship, from code quality and audit readiness to the clarity of what we publish, and we treat a careless sentence as seriously as a careless function.
In practice. Automated checks compare every published figure against the content hub and fail the build on a mismatch, so a wrong number cannot reach a visitor.
Security By Structure
We prefer protections that hold because of how a system is arranged rather than because everybody remembered the procedure. Structure survives a bad day; procedure often does not.
In practice. Identity, custody, asset records and validator operations are separate authorities with separate codebases, so no single component can both establish who you are and move what you hold.
Measured, Not Asserted
We publish what can be checked. A figure that cannot be traced to a running system or a filed document does not belong on a page that asks anyone to make a decision.
In practice. Metrics we cannot evidence are left off this site entirely, including figures the parent company publishes about itself, rather than repeated because they look good.
The Company, In Figures
Four of these are read from the running networks and republished automatically. The rest are corporate facts stated once and used everywhere on this site.
Licensed Where It Matters, Separated By Design
Regulated activity sits in the entity licensed to perform it, systems are built to the control frameworks their sector expects, and the authorities inside the ecosystem are held deliberately apart.
Registration Held
The group's Canadian entity holds a Money Services Business registration covering virtual currency services, payment service provision and foreign exchange. Regulated money movement runs through that entity and against its compliance programme, and those obligations set the floor for how identity is handled everywhere else in the ecosystem.
What The Registration Obliges
Frameworks Engineered To
Systems are built against the control frameworks their sector requires, so a client's own audit finds the evidence it expects where it expects it. This is an engineering standard, stated as such, and not a claim that a certificate is held against each name.
Separation Of Authority
Four authorities, four domains, no overlap. No single component can both establish who somebody is and move what they hold.
SWSS IVL
Authentication, KYC, KYB and credentials. Holds no balance and moves nothing.
SWSS App
Wallet, staking and treasury movement, under an identity IVL established.
SWSS RWAX
DEED-1 instruments and the exchange data around them.
SWSS NodeX
Who may produce a block, decided in one place and on the record.
Go One Level Deeper
How the company is led and how it builds, or the technical specification that defines the network. Both are published in full, and neither asks to be taken on trust.