<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Core Concepts on Troposphere Docs</title><link>https://docs.troposphere.cloud/docs/concepts/</link><description>Recent content in Core Concepts on Troposphere Docs</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2024-2026 Troposphere</copyright><lastBuildDate>Sat, 28 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://docs.troposphere.cloud/docs/concepts/index.xml" rel="self" type="application/rss+xml"/><item><title>Connections</title><link>https://docs.troposphere.cloud/docs/concepts/connections/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/connections/</guid><description>&lt;p&gt;A connection represents a linked cloud provider account within Troposphere. Connections are the entry point for all data in the platform &amp;ndash; without them, there are no resources or costs to manage.&lt;/p&gt;</description></item><item><title>Resources</title><link>https://docs.troposphere.cloud/docs/concepts/resources/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/resources/</guid><description>&lt;p&gt;Resources are the cloud assets discovered automatically from your connected provider accounts. Every virtual machine, database, storage resource, network interface, and managed service appears as a resource in Troposphere, giving you a single searchable inventory of your estate.&lt;/p&gt;</description></item><item><title>Cost Buckets</title><link>https://docs.troposphere.cloud/docs/concepts/cost-buckets/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/cost-buckets/</guid><description>&lt;p&gt;Cost buckets are the primary mechanism for organising and allocating cloud costs in Troposphere. They let you map your cloud spend to the structure that matters to your business &amp;ndash; whether that is by team, project, environment, or cost center.&lt;/p&gt;</description></item><item><title>Principals</title><link>https://docs.troposphere.cloud/docs/concepts/principals/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/principals/</guid><description>&lt;p&gt;A &lt;strong&gt;principal&lt;/strong&gt; is any identity that can be granted access to resources in your cloud provider &amp;ndash; a user, a group, a service account, or a federated identity. Troposphere imports the principal directory from every connected cloud provider so you can see who or what has access to your estate, independent of the resources themselves.&lt;/p&gt;</description></item><item><title>Policies</title><link>https://docs.troposphere.cloud/docs/concepts/policies/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/policies/</guid><description>&lt;p&gt;Policies are compliance rules that continuously evaluate your cloud resources against criteria you define. They help enforce organisational standards &amp;ndash; such as requiring encryption on storage, restricting instance sizes, or mandating specific tags &amp;ndash; across all connected providers.&lt;/p&gt;</description></item><item><title>Policy Packs</title><link>https://docs.troposphere.cloud/docs/concepts/policy-packs/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/policy-packs/</guid><description>&lt;p&gt;Policy Packs are curated collections of policy rules that enforce a specific compliance framework. Rather than authoring every rule yourself, your organisation subscribes to a pack and inherits the rules it contains. Packs are maintained by Troposphere, so they stay current as the underlying framework evolves.&lt;/p&gt;</description></item><item><title>Insights</title><link>https://docs.troposphere.cloud/docs/concepts/insights/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/insights/</guid><description>&lt;p&gt;Insights are automated, pre-built checks that evaluate your cloud resources against established best practices. Unlike policies, which you define yourself, insights are maintained by Troposphere and updated as provider recommendations evolve.&lt;/p&gt;</description></item><item><title>Alerts</title><link>https://docs.troposphere.cloud/docs/concepts/alerts/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/alerts/</guid><description>&lt;p&gt;Alerts are notifications generated by the platform when something requires your attention. They provide a unified feed of issues across cost, compliance, and operational health.&lt;/p&gt;</description></item><item><title>Organisations</title><link>https://docs.troposphere.cloud/docs/concepts/organisations/</link><pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate><guid>https://docs.troposphere.cloud/docs/concepts/organisations/</guid><description>&lt;p&gt;Organisations are the top-level containers in Troposphere. Every connection, resource, cost bucket, policy, and alert belongs to an organisation. They provide the multi-tenancy boundary that keeps data isolated between different teams or companies.&lt;/p&gt;</description></item></channel></rss>