Alpha — Editor in development

Declarative infrastructure. Multi-cloud. Graph-first.

InClouds provides tooling to model, validate, and deploy complex infrastructure across AWS, GCP, Azure, and hybrid environments using TOSCA as the canonical representation — before Terraform is ever written.

  • Intent-driven design separated from execution target
  • Graph traversal → Terraform generation pipeline
  • Provider-agnostic topology with consistency enforcement
  • RAG-assisted TOSCA component retrieval
targets:AWSGCPAzureHybrid
Core capabilities

The engineering decisions behind InClouds

Declarative

Intent before execution

TOSCA defines what you want, not how to provision it. Infrastructure intent is expressed as typed node templates and relationship definitions. Terraform is a compilation target, not the source of truth.

node_templates:
  web_cluster:
    type: tosca.nodes.Compute
    capabilities:
      host:
        properties:
          num_cpus: 4
          mem_size: 16 GB
Graph-based

Topology as a graph

Infrastructure relationships are first-class. Dependencies, network paths, IAM bindings, and placement constraints are encoded as directed edges in a typed property graph — traversable, validatable, and diffable.

relationships:
  - type: tosca.relationships.ConnectsTo
    source: api_gateway
    target: compute_cluster
    interfaces:
      Configure:
        pre_configure_target: scripts/tls.sh
Multi-cloud

Provider-agnostic topology

The same TOSCA model compiles to AWS CloudFormation mappings, GCP Deployment Manager, or Azure ARM — with a consistency layer that enforces naming, tagging, and network segmentation policies across providers.

topology_template:
  inputs:
    cloud_provider:
      type: string
      constraints:
        - valid_values: [aws, gcp, azure]
Architecture

From model to deployment

The pipeline is deterministic and reproducible. Each stage has explicit contracts. Nothing is implicit. Infrastructure state is always derivable from the model.

01

Model

Author topology as TOSCA node templates, capabilities, and relationships.

02

Retrieve

RAG pipeline resolves typed TOSCA components from catalog — validated against schema.

03

Validate

Graph traversal verifies dependency closure, cyclic detection, and constraint satisfaction.

04

Compile

Provider-specific Terraform HCL is generated from the resolved graph — not hand-authored.

05

Deploy

Orchestrator applies the plan across target providers with rollback on failure.

Open Source

Elassandra maintenance continues

InClouds maintains the Elassandra project — Apache Cassandra 4.0.x with OpenSearch 1.3.x integration — for production teams requiring combined NoSQL + full-text search without operational complexity.