A client's system is set up after the agreement is signed.
What the client owns, and what it licenses
The client owns its data, its Ontology and its custom code; it licenses the Siege platform its system runs on.
What | What it means |
|---|---|
Its data | The data layer is the client's own PostgreSQL database, which no other client shares. |
Its Ontology | The model of the client's business, in open W3C standards (RDF and Turtle), so any standard ontology tool can read the file without Siege. |
Its Choreographs | The order of the client's work, drawn by Siege from how the business works, kept in the client's repository beside its Ontology. |
Its custom code | The screens, reports, connections and tests built for the client, with their documentation and their history from the client's first commit. |
Its repository | The client's repository starts clean: its own code, no third-party or Siege-internal history. It sits in the client's own account. |
To check: open the client's repository and database in the client's own accounts, and open the exported Ontology in any standard ontology tool.
How the license works
Stage | What it is |
|---|---|
The Foundation Model engagement | Siege models the business, builds the foundation and the first software on it, and connects real data once the data agreement is signed. |
A renewable yearly license | The client's own instance of the Siege platform, renewed each year, including support and updates. |
License term | What it allows |
|---|---|
Scope | The client's own business, including its affiliates |
Use | Run, copy, and build new software on the instance |
Contractors | Any team the client chooses may work on the instance, under confidentiality |
Not permitted | Reselling the platform, or offering it to others |
What the client receives
Everything needed to run the system, change it, and leave: its data, its Ontology in open standards, its Choreographs, its custom code and repository, its licensed instance, and the documentation and runbooks that explain them. The client holds all of it on every path below.
Two paths
A client does not need to keep working with Siege. Every client chooses one of two paths.
Path | Who changes what | What keeps the system sound |
|---|---|---|
Managed | Siege is the licensed firm on the system and does the work. | While Siege is the licensed firm, Siege's method and compliance stay in. Every change passes Siege's full checks before it ships, and Siege always upholds its standards. |
Total Freedom | The client breaks off and is fully independent. Its own engineers can change anything, and the client owns the result. | Siege's compliance comes off by a choice the client signs. The client's own team builds its own checks and compliance, so that its changes do not break things. Sign-in, permissions and the limits on each agent ship switched on, and Siege recommends they stay on. |
A client that leaves Siege is on its own. Coming back is paid work to bring the system back into line, and Siege cannot promise to undo what another team has changed.
If the license is not renewed
The client's system keeps running as it stands, for good. Only Siege's support and updates stop. Renewing buys another year of support, updates and new work.
Siege's FDE account
Siege's FDEs sign in through Siege's FDE account. Under the license it cannot be removed. It needs two-step sign-in, it takes actions under the same checks as everyone else, every sign-in and every change made through it is visible to the client's administrators, and what it may be used for is limited by the agreement. It stays in place while the license runs. If the client does not renew, the FDE account is switched off at the end of the license, and it comes back only if the client renews or asks for paid help.