@fractal_cloud/sdk 1.3.0 → 1.4.0

package/LICENSE

@@ -1,5 +1,5 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
 
  Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
@@ -7,17 +7,15 @@
 
                             Preamble
 
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
 
   The licenses for most software and other practical works are designed
 to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
+our General Public Licenses are intended to guarantee your freedom to
 share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  You can apply it to
-your programs, too.
+software for all its users.
 
   When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
@@ -26,44 +24,34 @@ them if you wish), that you receive source code or can get it if you
 want it, that you can change the software or use pieces of it in new
 free programs, and that you know you can do these things.
 
-  To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  You must make sure that they, too, receive
-or can get the source code.  And you must show them these terms so they
-know their rights.
-
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
 
   The precise terms and conditions for copying, distribution and
 modification follow.
@@ -72,7 +60,7 @@ modification follow.
 
   0. Definitions.
 
-  "This License" refers to version 3 of the GNU General Public License.
+  "This License" refers to version 3 of the GNU Affero General Public License.
 
   "Copyright" also means copyright-like laws that apply to other kinds of
 works, such as semiconductor masks.
@@ -549,35 +537,45 @@ to collect a royalty for further conveying from those to whom you convey
 the Program, the only way you could satisfy both those terms and this
 License would be to refrain entirely from conveying the Program.
 
-  13. Use with the GNU Affero General Public License.
+  13. Remote Network Interaction; Use with the GNU General Public License.
+
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
 
   Notwithstanding any other provision of this License, you have
 permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
+under version 3 of the GNU General Public License into a single
 combined work, and to convey the resulting work.  The terms of this
 License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
 
   14. Revised Versions of this License.
 
   The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
+the GNU Affero General Public License from time to time.  Such new versions
+will be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.
 
   Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU General
+Program specifies that a certain numbered version of the GNU Affero General
 Public License "or any later version" applies to it, you have the
 option of following the terms and conditions either of that numbered
 version or of any later version published by the Free Software
 Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
+GNU Affero General Public License, you may choose any version ever published
 by the Free Software Foundation.
 
   If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
+versions of the GNU Affero General Public License can be used, that proxy's
 public statement of acceptance of a version permanently authorizes you
 to choose that version for the Program.
 
@@ -635,40 +633,29 @@ the "copyright" line and a pointer to where the full notice is found.
     Copyright (C) <year>  <name of author>
 
     This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
+    it under the terms of the GNU Affero General Public License as published by
     the Free Software Foundation, either version 3 of the License, or
     (at your option) any later version.
 
     This program is distributed in the hope that it will be useful,
     but WITHOUT ANY WARRANTY; without even the implied warranty of
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
+    GNU Affero General Public License for more details.
 
-    You should have received a copy of the GNU General Public License
+    You should have received a copy of the GNU Affero General Public License
     along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 Also add information on how to contact you by electronic and paper mail.
 
-  If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-    <program>  Copyright (C) <year>  <name of author>
-    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, your program's commands
-might be different; for a GUI interface, you would use an "about box".
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
 
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
+For more information on this, and how to apply and follow the GNU AGPL, see
 <https://www.gnu.org/licenses/>.
-
-  The GNU General Public License does not permit incorporating your program
-into proprietary programs.  If your program is a subroutine library, you
-may consider it more useful to permit linking proprietary applications with
-the library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.  But first, please read
-<https://www.gnu.org/licenses/why-not-lgpl.html>.

package/README.md

@@ -41,8 +41,22 @@ A Live System is a running instance of a Fractal. It maps each abstract blueprin
 - Definition of Live Systems with typed, provider-specific helpers
 - Deployment of Live Systems to any Fractal Cloud Environment
 - Personal and organisation-owned accounts
-- **IaaS helpers** for AWS, Azure, GCP, OCI, and Hetzner
-- **PaaS helpers** for AWS (ECS, EKS), Azure (AKS, Container Apps Environment, Container Instance, Container App), GCP (GKE, Cloud Run), and OCI (Container Instance)
+
+### Infrastructure domains
+
+| Domain | Blueprint types | Live system offers | Providers |
+|--------|----------------|-------------------|-----------|
+| **NetworkAndCompute** | VirtualNetwork, Subnet, SecurityGroup, VirtualMachine, ContainerPlatform | 31 offers | AWS, Azure, GCP, OCI, Hetzner, VMware, OpenShift |
+| **CustomWorkloads** | Workload | Satisfied by PaaS/CaaS offers (ECS, Container Apps, Cloud Run, OpenShift, etc.) | AWS, Azure, GCP, OCI, OpenShift |
+| **Storage** | FilesAndBlobs, RelationalDbms, RelationalDatabase, DocumentDbms, DocumentDatabase, ColumnOrientedDbms, ColumnOrientedEntity, KeyValueDbms, KeyValueEntity, GraphDbms, GraphDatabase, Search, SearchEntity, Unmanaged | 23 offers | AWS, Azure, GCP, CaaS, SaaS |
+| **Messaging** | Broker, Entity (PaaS + CaaS), Unmanaged | 12 offers | Azure, GCP, CaaS |
+| **BigData** | DistributedDataProcessing, ComputeCluster, DataProcessingJob, MlExperiment, Datalake, Unmanaged | 16 offers | AWS, Azure, GCP |
+| **APIManagement** | PaaS ApiGateway, CaaS ApiGateway, Unmanaged | 6 offers | AWS, Azure, GCP, CaaS |
+| **Observability** | Monitoring, Tracing, Logging, Unmanaged | 4 offers | CaaS |
+| **Security** | ServiceMesh, Unmanaged | 2 offers | CaaS |
+| **Custom** | Any (via `Custom.blueprint()`) | Any (via `Custom.offer()`) | Any |
+
+> Custom aria agents can register additional domains, services, and offers beyond this built-in set. See [Custom Aria Components](#custom-aria-components) below.
 
 ## Installation
 
@@ -215,42 +229,291 @@ Best for: **CI/CD pipelines** where the pipeline must not advance until infrastr
 
 The same blueprint can be deployed on any supported provider. Live system files are short and only contain vendor-specific parameters — all structural decisions (dependencies, traffic rules, security rules) stay in the blueprint.
 
-| Blueprint component | AWS | Azure | GCP | OCI | Hetzner |
-|---------------------|-----|-------|-----|-----|---------|
-| `VirtualNetwork` | `AwsVpc` | `AzureVnet` | `GcpVpc` | `OciVcn` | `HetznerNetwork` |
-| `Subnet` | `AwsSubnet` | `AzureSubnet` | `GcpSubnet` | `OciSubnet` | `HetznerSubnet` |
-| `SecurityGroup` | `AwsSecurityGroup` | `AzureNsg` | `GcpFirewall` | `OciSecurityList` | `HetznerFirewall` |
-| `VirtualMachine` | `Ec2Instance` | `AzureVm` | `GcpVm` | `OciInstance` | `HetznerServer` |
+### IaaS
+
+| Blueprint component | AWS | Azure | GCP | OCI | Hetzner | VMware | OpenShift |
+|---------------------|-----|-------|-----|-----|---------|--------|-----------|
+| `VirtualNetwork` | `AwsVpc` | `AzureVnet` | `GcpVpc` | `OciVcn` | `HetznerNetwork` | `VspherePortGroup` | — |
+| `Subnet` | `AwsSubnet` | `AzureSubnet` | `GcpSubnet` | `OciSubnet` | `HetznerSubnet` | `VsphereVlan` | — |
+| `SecurityGroup` | `AwsSecurityGroup` | `AzureNsg` | `GcpFirewall` | `OciSecurityList` | `HetznerFirewall` | — | `OpenshiftSecurityGroup` |
+| `VirtualMachine` | `Ec2Instance` | `AzureVm` | `GcpVm` | `OciInstance` | `HetznerServer` | `VsphereVm` | `OpenshiftVm` |
+
+### PaaS / CaaS
+
+| Blueprint component | AWS | Azure | GCP | OCI | OpenShift |
+|---------------------|-----|-------|-----|-----|-----------|
+| `ContainerPlatform` | `AwsEcsCluster` · `AwsEksCluster` | `AzureAksCluster` · `AzureContainerAppsEnvironment` | `GcpGkeCluster` | — | — |
+| `Workload` | `AwsEcsTaskDefinition` + `AwsEcsService` | `AzureContainerInstance` · `AzureContainerApp` | `GcpCloudRunService` | `OciContainerInstance` | `OpenshiftWorkload` |
+
+### OpenShift-specific offers
+
+| Offer | Type string | Blueprint equivalent |
+|-------|-------------|---------------------|
+| `OpenshiftService` | `NetworkAndCompute.CaaS.OpenshiftService` | Kubernetes Service + Route (standalone) |
+| `OpenshiftPersistentVolume` | `Storage.CaaS.OpenshiftPersistentVolume` | Persistent Volume Claim (standalone) |
+
+### Storage
+
+| Blueprint component | AWS | Azure | GCP | CaaS |
+|---------------------|-----|-------|-----|------|
+| `FilesAndBlobs` | `AwsS3` | `AzureStorageAccount` · `AzureBlobContainer` · `AzureFileStorage` | `GcpCloudStorage` | — |
+| `RelationalDbms` | — | `AzurePostgreSqlDbms` · `AzureCosmosDbAccount` | `GcpPostgreSqlDbms` | — |
+| `RelationalDatabase` | — | `AzurePostgreSqlDatabase` · `AzureCosmosDbPostgreSqlDatabase` | `GcpPostgreSqlDatabase` | — |
+| `DocumentDbms` | — | `AzureCosmosDbAccount` | `GcpFirestore` | — |
+| `ColumnOrientedDbms` | — | `AzureCosmosDbCassandra` | `GcpBigTable` | — |
+| `Search` | — | — | — | `Elastic` |
+
+### BigData
+
+| Blueprint component | AWS | Azure | GCP |
+|---------------------|-----|-------|-----|
+| `DistributedDataProcessing` | `AwsDatabricks` | `AzureDatabricks` | `GcpDatabricks` |
+| `ComputeCluster` | `AwsDatabricksCluster` | `AzureDatabricksCluster` | `GcpDatabricksCluster` |
+| `DataProcessingJob` | `AwsDatabricksJob` | `AzureDatabricksJob` | `GcpDatabricksJob` |
+| `MlExperiment` | `AwsDatabricksMlflow` | `AzureDatabricksMlflow` | `GcpDatabricksMlflow` |
+| `Datalake` | `AwsS3Datalake` | `AzureDatalake` | `GcpDatalake` |
+
+## Custom Aria Components
+
+Enterprise customers running custom aria agents can extend the SDK with their own infrastructure domains, service delivery models, and component types — no fork required.
+
+### Defining custom component types
+
+Use `Custom.blueprint()` and `Custom.offer()` to create reusable factories. Each factory stamps out components of a specific type, just like the built-in helpers (`VirtualNetwork`, `AwsVpc`, etc.).
+
+```typescript
+import {
+  Custom, Fractal, LiveSystem, ServiceDeliveryModel,
+} from '@fractal_cloud/sdk';
+
+// ── 1. Define factories (once per type, reusable) ─────────────────────────
+
+const TimeSeriesStore = Custom.blueprint({
+  domain: 'Analytics',                       // any string — not limited to built-in domains
+  serviceDeliveryModel: ServiceDeliveryModel.PaaS,
+  name: 'TimeSeriesStore',                   // must be PascalCase
+});
+
+const InfluxDb = Custom.offer({
+  domain: 'Analytics',
+  serviceDeliveryModel: ServiceDeliveryModel.PaaS,
+  name: 'InfluxDb',
+  provider: 'CustomProvider',                // any string — not limited to built-in providers
+});
+```
+
+### Creating blueprint components (cloud-agnostic)
+
+```typescript
+// ── 2. Blueprint — what the architecture needs ────────────────────────────
+
+const metricsDb = TimeSeriesStore.create({
+  id: 'metrics-db',
+  version: { major: 1, minor: 0, patch: 0 },
+  displayName: 'Metrics Database',
+  parameters: { retentionDays: '90', replicationFactor: '3' },
+});
+```
+
+### Satisfying with a custom offer (vendor-specific)
+
+The `satisfy()` method works exactly like built-in offers: it locks the blueprint's id, version, displayName, description, dependencies, links, and parameters, then exposes only vendor-specific parameter setters.
+
+```typescript
+// ── 3. Live system — how the architecture is provisioned ──────────────────
 
-PaaS and CaaS helpers are also available for the agnostic `ContainerPlatform` / `Workload` blueprint types, with provider-specific satisfiers across AWS, Azure, GCP, and OCI:
+const influx = InfluxDb.satisfy(metricsDb)
+  .withParameter('bucket', 'metrics')
+  .withParameter('orgId', 'my-org')
+  .build();
+```
+
+### Standalone creation (without a blueprint)
+
+If you don't need the blueprint-satisfy flow, create live system components directly:
+
+```typescript
+const influx = InfluxDb.create({
+  id: 'metrics-db',
+  version: { major: 1, minor: 0, patch: 0 },
+  displayName: 'Metrics Database',
+  parameters: { bucket: 'metrics', orgId: 'my-org' },
+});
+```
+
+### Using the fluent builder
 
-| Blueprint component | AWS | Azure | GCP | OCI |
-|---------------------|-----|-------|-----|-----|
-| `ContainerPlatform` | `AwsEcsCluster` · `AwsEksCluster` | `AzureAksCluster` · `AzureContainerAppsEnvironment` | `GcpGkeCluster` | — |
-| `Workload` | `AwsEcsTaskDefinition` + `AwsEcsService` | `AzureContainerInstance` · `AzureContainerApp` | `GcpCloudRunService` | `OciContainerInstance` |
+For advanced scenarios (dependencies, links, conditional params), use the builder API:
+
+```typescript
+const metricsDb = TimeSeriesStore.getBuilder()
+  .withId('metrics-db')
+  .withVersion(1, 0, 0)
+  .withDisplayName('Metrics Database')
+  .withParameter('retentionDays', '90')
+  .withDependencies([{ id: someOtherComponent.id }])
+  .withLinks([{ id: anotherComponent.id, parameters: linkParams }])
+  .build();
+```
+
+### Deploying custom components
+
+Custom components integrate seamlessly with the standard deploy flow:
+
+```typescript
+// ── 4. Deploy as usual ────────────────────────────────────────────────────
+
+const fractal = Fractal.getBuilder()
+  .withId(fractalId)
+  .withComponents([metricsDb])
+  .build();
+
+const liveSystem = LiveSystem.getBuilder()
+  .withId(liveSystemId)
+  .withFractalId(fractal.id)
+  .withGenericProvider('CustomProvider')
+  .withEnvironment(environment)
+  .withComponent(influx)
+  .build();
+
+await fractal.deploy(credentials);
+await liveSystem.deploy(credentials, { mode: 'wait' });
+```
+
+### Mixing custom and built-in components
+
+Custom components can coexist with built-in ones in the same Fractal:
+
+```typescript
+import { VirtualNetwork, Subnet, Custom, ServiceDeliveryModel } from '@fractal_cloud/sdk';
+
+const MyCache = Custom.blueprint({
+  domain: 'Performance',
+  serviceDeliveryModel: ServiceDeliveryModel.PaaS,
+  name: 'DistributedCache',
+});
+
+const network = VirtualNetwork.create({ /* ... */ })
+  .withSubnets([
+    Subnet.create({ /* ... */ }),
+  ]);
+
+const cache = MyCache.create({
+  id: 'app-cache',
+  version: { major: 1, minor: 0, patch: 0 },
+  displayName: 'Application Cache',
+  parameters: { maxMemoryMb: '4096', evictionPolicy: 'lru' },
+  dependencies: [{ id: network.vpc.id }],   // depend on built-in components
+});
+
+const fractal = Fractal.getBuilder()
+  .withId(fractalId)
+  .withComponents([...network.components, cache])
+  .build();
+```
+
+### API reference
+
+| Function | Returns | Description |
+|----------|---------|-------------|
+| `Custom.blueprint(config)` | `CustomBlueprintFactory` | Define a reusable blueprint component type |
+| `Custom.offer(config)` | `CustomOfferFactory` | Define a reusable live system offer type |
+
+**`CustomBlueprintFactory`**
+
+| Method | Returns | Description |
+|--------|---------|-------------|
+| `.create(config)` | `BlueprintComponent` | Create a component with id, version, displayName, parameters, dependencies, links |
+| `.getBuilder()` | `CustomBlueprintBuilder` | Fluent builder with `withParameter(key, value)`, `withDependencies()`, `withLinks()` |
+| `.typeString` | `string` | The full type string (e.g. `"Analytics.PaaS.TimeSeriesStore"`) |
+
+**`CustomOfferFactory`**
+
+| Method | Returns | Description |
+|--------|---------|-------------|
+| `.create(config)` | `LiveSystemComponent` | Create a live system component directly |
+| `.getBuilder()` | `CustomOfferBuilder` | Fluent builder with full access to all fields |
+| `.satisfy(blueprint)` | `CustomSatisfiedBuilder` | Lock structural fields from blueprint; only `withParameter()`/`withParameters()` exposed |
+| `.typeString` | `string` | The full type string (e.g. `"Analytics.PaaS.InfluxDb"`) |
+
+**`CustomSatisfiedBuilder`** (returned by `satisfy()`)
+
+| Method | Returns | Description |
+|--------|---------|-------------|
+| `.withParameter(key, value)` | `CustomSatisfiedBuilder` | Add a single vendor-specific parameter |
+| `.withParameters(record)` | `CustomSatisfiedBuilder` | Add multiple vendor-specific parameters at once |
+| `.build()` | `LiveSystemComponent` | Build the final component |
+
+### Validation
+
+- **Component name** must be PascalCase (e.g. `TimeSeriesStore`, `InfluxDb`). Validated eagerly when the factory is created — a `SyntaxError` is thrown immediately for invalid names.
+- **Component id** must be kebab-case (e.g. `metrics-db`). Each segment must start with a letter.
+- **Domain and provider** accept any string. Built-in values (`InfrastructureDomain.Storage`, `'AWS'`, etc.) provide autocomplete but are not enforced.
+- Custom domains and providers must be registered with the Fractal Cloud platform for deployment to succeed.
+
+---
 
 ## Samples
 
 The [sample repository](https://github.com/Fractal-Cloud/fractal-ts-sdk-samples) contains ready-to-run examples:
 
-| Sample | Description |
-|--------|-------------|
-| `basic_iaas` | VPC + Subnet + Security Group + two VMs — deploys on AWS, Azure, GCP, OCI, or Hetzner via `CLOUD_PROVIDER` env var |
-| `basic_container_platform` | VPC + Subnet + Security Group + container platform + two workloads — deploys on AWS (ECS Fargate), Azure (Container Apps), or GCP (Cloud Run) via `CLOUD_PROVIDER` env var |
+| Sample | Providers | Description |
+|--------|-----------|-------------|
+| `basic_iaas` | AWS · Azure · GCP · OCI · Hetzner | VPC + Subnet + Security Group + two VMs |
+| `basic_container_platform` | AWS · Azure · GCP | VPC + Subnet + SG + container platform + two workloads |
+| `basic_cicd` | AWS | CI/CD pipeline deployment with wait mode |
+| `basic_storage` | AWS · Azure · GCP | PostgreSQL DBMS + Database + object storage |
+| `basic_messaging` | Azure · GCP | Message broker + two topics |
+| `basic_big_data` | AWS · Azure · GCP | Databricks workspace + cluster + job + MLflow |
+| `basic_api_management` | AWS · Azure · GCP | API Gateway |
+| `basic_observability` | CaaS | Monitoring + tracing + logging (Prometheus, Jaeger, Elastic) |
+| `basic_security` | CaaS | Service mesh (Ocelot) |
 
 ## Architecture
 
 ```
 src/
+  custom/            # Custom aria component factories (Custom.blueprint, Custom.offer)
   fractal/           # Cloud-agnostic blueprint helpers
     component/
-      network_and_compute/iaas/   # VirtualNetwork, Subnet, SecurityGroup, VirtualMachine
-      network_and_compute/paas/   # ContainerPlatform
-      custom_workloads/caas/      # Workload
+      network_and_compute/   # VirtualNetwork, Subnet, SecurityGroup, VirtualMachine, ContainerPlatform
+      custom_workloads/      # Workload
+      storage/               # FilesAndBlobs, RelationalDbms, DocumentDbms, Search, etc.
+      messaging/             # Broker, Entity
+      big_data/              # DistributedDataProcessing, ComputeCluster, DataProcessingJob, etc.
+      api_management/        # ApiGateway
+      observability/         # Monitoring, Tracing, Logging
+      security/              # ServiceMesh
   live_system/       # Provider-specific helpers
     component/
-      network_and_compute/iaas/   # AWS, Azure, GCP, OCI, Hetzner components
-      network_and_compute/paas/   # AWS (ECS, EKS), Azure (AKS, Container Apps, Container Instance), GCP (GKE, Cloud Run), OCI (Container Instance)
+      network_and_compute/   # AWS, Azure, GCP, OCI, Hetzner, VMware (IaaS) + OpenShift (CaaS) + AWS/Azure/GCP (PaaS)
+      custom_workloads/      # OpenShift (CaaS)
+      storage/               # AWS S3, Azure Storage/CosmosDB/PostgreSQL, GCP Storage/Firestore/BigTable, OpenShift PV
+      messaging/             # Azure ServiceBus/EventHub, GCP PubSub, CaaS Kafka
+      big_data/              # AWS/Azure/GCP Databricks + Datalake
+      api_management/        # AWS CloudFront, Azure API Management, GCP API Gateway, CaaS Ambassador/Traefik
+      observability/         # CaaS Prometheus, Jaeger, Elastic
+      security/              # CaaS Ocelot
+```
+
+## Debug logging
+
+Set `FRACTAL_DEBUG=true` to log every outbound HTTP request and every inbound response to stdout. This covers all API calls made by `fractal.deploy()`, `liveSystem.deploy()`, `fractal.destroy()`, and `liveSystem.destroy()`.
+
+```
+[2026-03-11T14:23:00Z] DEBUG → GET https://api.fractal.cloud/livesystems/my-ls
+[2026-03-11T14:23:00Z] DEBUG ← 404 GET https://api.fractal.cloud/livesystems/my-ls  body=null
+[2026-03-11T14:23:00Z] DEBUG → POST https://api.fractal.cloud/livesystems  body={"liveSystemId":"..."}
+[2026-03-11T14:23:00Z] DEBUG ← 201 POST https://api.fractal.cloud/livesystems  body=null
+```
+
+- Authentication headers (`X-ClientID`, `X-ClientSecret`) are never logged.
+- Request and response bodies are truncated to 2 000 characters.
+- Both success and error responses are logged.
+- Works in all deploy modes (`fire-and-forget` and `wait`).
+
+```bash
+FRACTAL_DEBUG=true node build/src/index.js
 ```
 
 ## Contributing and feedback
@@ -261,7 +524,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for contribution guidelines. Use GitHub I
 
 ## License
 
-Licensed under GPLv3. See the [LICENSE](LICENSE) file for details.
+Licensed under AGPLv3. See the [LICENSE](LICENSE) file for details.
 
 Made with ❤️ by the Fractal Cloud team.