GiolitLabs
Developer Center

Build secure, isolated business modules.

Create specialized backend modules that run inside hardware-restricted environments. Define data columns, network policies, and API tunnels using standard declarative manifest rulesets.

Launch Developer PortalRead Documentation

Declarative manifest schemas

Every module defines its capabilities, endpoints, and external dependencies in a declarative `manifest.xml` file. The platform uses this manifest to register API routes and verify integration boundaries.

The Developer Portal statically validates namespacing, checks version compatibility, and enforces license entitlements during activation.

1<?xml version=<span class="text-emerald-400">"1.0"</span> encoding=<span class="text-emerald-400">"UTF-8"</span>?>
2<ModuleManifest>
3 <!-- Module metadata -->
4 <name>acme-cardiology</name>
5 <version>1.2.4</version>
6 <contextPath>/api/acme/cardiology</contextPath>
7 
8 <!-- Exposed Public APIs -->
9 <publicApis>
10 <api>
11 <path>/reports/{reportId}</path>
12 <method>GET</method>
13 <requiredRole>CARDIOLOGIST</requiredRole>
14 </api>
15 </publicApis>
16 
17 <!-- Module dependencies -->
18 <dependencies>
19 <dependency>
20 <name>patient-registration</name>
21 <versionRange>[1.0.0, 2.0.0)</versionRange>
22 </dependency>
23 </dependencies>
24</ModuleManifest>
Sandbox Compiler Console
No compile sessions. Click 'Compile & Test' above.

Module Compilation & Communication Architecture

Understand the step-by-step lifecycles of module registration and runtime routing inside our isolated network boundaries.

Phase 01

Giolit DSL & Manifest Compilation Pipeline

Step A / DEFINE

Specify Manifest & DSL

Developers define endpoint mappings in `manifest.xml`, write custom code configurations in Giolit DSL (`.gldsl`), and implement module features.

Step B / COMPILE

Giolit DSL Engine

The compilation engine parses the manifest structure and compiles the DSL logic to generate proper, standalone running modules or features.

Step C / SUBSCRIBE

Consumer Subscriptions

Completed and audited features are registered in the store, allowing consumers to dynamically subscribe to modules as necessary.

Phase 02

Secure Inter-Module Request Routing

All business modules run fully isolated. If an active module (such as cardiology diagnostics) requires resource data from a dependent module (such as patient registration), the request is proxy-routed and audited securely in transit.

acme-cardiologyRequesting Module
GET /patients/102
Audited Transit
Giolit Safe Transit Proxy
Verifies caller roles, active licenses, and module dependencies
patient-registrationTarget Dependency
200 OK (Secure Payload)

Core developer guidelines

Follow these parameters to structure and list modules cleanly inside our marketplace.

1. Specify Manifest & DSL

Specify variables and parameters in your XML manifest (manifest.xml) and write custom operations logic using Giolit DSL (.gldsl).

2. Portal Verification

Upload configurations to the Portal, where the controller statically checks namespace prefixes and external module dependency scopes.

3. DSL Engine Compilation

Giolit's compiler compiles the validated manifest and DSL code, runs static safety checks, and builds finished deployable modules.

4. List & Monetize

Publish your finished, audited modules directly to the marketplace catalog to offer subscription licenses to corporate clients.