Welcome to rescile

From Complexity to Clarity — Build a Living Blueprint of Your Hybrid World.

In today’s IT landscape, critical information is scattered everywhere—across cloud consoles, CMDBs, spreadsheets, and tribal knowledge. Answering seemingly simple questions like “What’s the full cost of this application?” or “What’s the blast radius if this database fails?” or “Where to get the parameters and dependencies for deployment from?” can become a frantic, cross-departmental fire drill.

rescile solves this by transforming scattered data into a single, unified, and queryable dependency graph. This is called a “digital twin”—a living blueprint of the entire hybrid estate, from on-premise hardware to cloud services and the code that runs on them. By adopting a “configuration-as-code” philosophy, rescile allows for defining, governing, and understanding infrastructure with unprecedented clarity, turning complex challenges into simple queries.

This approach creates a single source of truth that unlocks deep architectural insights, automates compliance, streamlines complex operational tasks and deployments.

This documentation guides users through the core concepts, from defining foundational assets to enforcing complex security policies.

The Core Workflow: From Assets to a Governed Graph

rescile builds the digital twin in a simple, declarative, and repeatable four-phase process. The facts, architectural rules, governance policies, and output definitions are provided as simple text files, and rescile constructs the intelligent graph.

1. Assets (The Facts): Start with what you have. Define the raw components of your environment—applications, databases, contracts, servers—in simple, human-readable CSV files. This is your ground truth, the foundational “who” and “what” of your world that anyone can contribute to. This data forms the initial set of resources in the graph.

2. Models (The Blueprints): Next, apply declarative architectural models written in TOML. These are the architectural blueprints that define how your resources connect and interact. They transform the raw facts into a rich, contextual graph by creating new resources, establishing complex relationships, and propagating data across connections.

3. Compliance (The Rules): Next, apply governance and security policies, also in TOML. These rules automatically mutate the graph to enforce the organization’s standards. This is like applying building codes to your blueprint—inserting firewalls, mandating encryption, and mapping ownership at scale.

4. Output (The Artifacts): Finally, define structured data outputs using TOML. These are declarative templates that query the rich, contextual graph to generate actionable artifacts. They transform the digital twin into standardized JSON or YAML output, such as service catalogs, compliance evidence, or configuration files for other tools.

The result is a comprehensive “digital twin” of the estate. A machine-readable model that is always in sync with your architectural intent ready to be queried and integrated into your automation and auditing workflows.

What You Gain: Unprecedented Insight and Automation

This living blueprint isn’t just a diagram; it’s an active tool that empowers the entire organization.

• Get Instant Answers: Answer complex, cross-domain questions in seconds. Instantly trace dependencies to perform impact analysis, attribute costs with precision, and identify every system affected by a vulnerability.

• Automate Governance: Turn audit preparation from a months-long manual effort into a continuous, automated query. Enforce architectural standards and security policies by design, not by chance.

• Drive Intelligent Automation: Use the graph as a single source of truth to generate configurations for tools like Terraform and Prometheus, create targeted remediation tickets, and validate that your deployed reality matches your blueprint.

Where to Go Next

To begin building a blueprint, two paths are available, designed for either a quick tour or a deep dive.