> ## Documentation Index > Fetch the complete documentation index at: https://docs.cord.nyc/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > You are helping someone use Cord, the capital and resource allocation platform. > Use title-case Cord in prose. Prefer workspace, project, ontology, lineage, scenario, and allocation. > Say source-backed or sourced for answers with lineage. Do not say hallucination-free. > Product URLs are https://app.cord.nyc, https://cord.nyc, and https://trust.cord.nyc. Support is support@cord.nyc. > Give concrete product steps. Do not invent UI labels, CLI commands, or unreleased agent runtime details. > Use Understanding Cord for concepts and Guides for task steps. # Apps > Full software applications, built by an agent on your business data. export const UnderstandingFlow = ({active}) => { const stages = [{ id: "ontology", label: "Ontology", detail: "business objects" }, { id: "functions", label: "Functions", detail: "shared calculations" }, { id: "apps", label: "Apps", detail: "operational interfaces" }]; return

{["light", "dark"].map(theme => )}

; }; ## What is a Cord app? An app in Cord is a full-stack software application built on your business logic and data. **Building a powerful, delightful app is the ultimate goal in Cord.** Even better if you build dozens. Cord apps are custom built around your company’s needs. When those apps help your team make better decisions and get things done, the company benefits. Apps are built entirely by agents. They are powered by [functions](/understanding-cord/functions), can run on live data, and connect to traditional and non-traditional systems of record. Cord apps represent the next era of how software is built, deployed, and maintained in an AI-native world. The examples below show dramatically different use cases at different companies, each built on the same foundations in Cord. ## One decision, start to finish Choose an example to see the question, the app, and the decisions it supports. ### Where should we invest in GPU capacity? US Compute Inc. is modeling data center investments. Its capacity investment Cord app helps the team test whether a site still makes money when demand softens, then build a capacity plan. Animated capacity investment app raising capital recovery from 10% to 20%, lowering utilization from 69% to 45%, then restoring both as economic profit and the break-even curve update

Animated capacity investment app raising capital recovery from 10% to 20%, lowering utilization from 69% to 45%, then restoring both as economic profit and the break-even curve update

Compare twelve candidate sites, then select a site to inspect its design options, revenue, energy cost, capital recovery, and economic profit. The map follows your selection, and the utilization curve shows how the site's break-even price changes as utilization changes. Animated site comparison selecting locations and swapping GPU designs, updating the map, break-even curve, and economic profit

Animated site comparison selecting locations and swapping GPU designs, updating the map, break-even curve, and economic profit

Switch between the base case and softer or stronger demand. Compare the portfolio totals and the selected site's break-even price, payback, and economic profit. Change the workload to see how the investment depends on what the capacity will serve. Animated capacity investment app changing demand scenarios and workloads, updating site rankings, map colors, portfolio totals, and site economics

Animated capacity investment app changing demand scenarios and workloads, updating site rankings, map colors, portfolio totals, and site economics

Open the app in Application Studio and ask the agent to explain the change using the app's figures. Follow how utilization, lease price, and capital recovery affect the result. Application Studio with the current capacity investment app on the left and the agent conversation on the right

Application Studio with the current capacity investment app on the left and the agent conversation on the right

In the plan builder, select a site and click a compute design to add it to the plan. Add more sites or swap individual designs, then compare investment, economic profit, and the tradeoff chart. Animated plan builder manually selecting compute designs for five sites and swapping individual GPUs, with the base scenario fixed as investment totals and the tradeoff chart update

Animated plan builder manually selecting compute designs for five sites and swapping individual GPUs, with the base scenario fixed as investment totals and the tradeoff chart update

### Which customers become less profitable as costs change? This app helps a team understand customer contribution and payback, test changes in margin and support cost, and inspect the customers affected. Review the saved results for 12,000 customers. Compare segments and identify customers whose payback period exceeds their segment's target. Customer economics app filtering the customer register by segment, region, and payback status, then returning to all customers

Customer economics app filtering the customer register by segment, region, and payback status, then returning to all customers

Move the support cost and gross margin sliders. Watch contribution, payback, and the customer heatmap update as you explore the impact on the portfolio. Customer economics app with support cost and gross margin sliders moving, updating the customer heatmap, contribution totals, customer rows, and the selected customer's payback curve

Customer economics app with support cost and gross margin sliders moving, updating the customer heatmap, contribution totals, customer rows, and the selected customer's payback curve

Select a customer to see the contribution breakdown and payback curve. Compare the plan with the what-if result and the segment target to understand what changed. Customer economics app selecting six customers with support cost held at 1.5 times plan, comparing their payback curves, contribution breakdowns, and segment targets

Customer economics app selecting six customers with support cost held at 1.5 times plan, comparing their payback curves, contribution breakdowns, and segment targets

In Application Studio, ask the agent to explain the result or revise the app to explore your next question. The preview stays beside the conversation. Application Studio with the app preview on the left and the agent chat on the right

Application Studio with the app preview on the left and the agent chat on the right

Every value along the way can be explained. In Application Studio, **Show calculations** outlines every value an app computed. Inspect one to see its equation, its operands, and the saved function it came from. The capacity investment app with Show calculations on, every computed value outlined in the primary color across the KPI tiles, the site table, and the selected site's economics

The capacity investment app with Show calculations on, every computed value outlined in the primary color across the KPI tiles, the site table, and the selected site's economics

Customer economics in Application Studio with Show calculations enabled and values outlined across portfolio totals, segments, customer rows, and the portfolio inspector

Apps take action as well as show information. Depending on what it was built for, an app can update a record, assign an account, approve a change, or record a decision, and that change flows back into the data every other app reads. ## Where the numbers come from The calculations behind an app are [functions](/understanding-cord/functions): saved business logic that runs over the [ontology](/understanding-cord/ontology), Cord's model of your business data, and stores its results. Two apps built on the same function show the same definition of contribution or payback. Each build reads specific saved results, so the version and inputs behind any number are always known. ## One function, many apps Because an agent builds apps, each team gets software shaped to how it works rather than one dashboard for everyone. The capacity investment app above reads a site break-even function. That same function could feed three more: | App | Who uses it | What it covers | | ---------------- | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Capital plan | FP\&A and the investment committee | Every proposed project with its spend, expected return, payback, and ROIC, ranked against the hurdle rate; scenarios on cost of capital and timing; approve, defer, or send back with a note | | Asset economics | Operations and plant finance | Each site, line, or fleet with contribution, utilization, maintenance capex against return, and the assets falling below their target; drill from a site to the orders and costs behind it | | Sources and uses | Corporate development | Acquisition targets with pro forma economics, synergy cases, financing mix, and a board-ready view; every figure traceable to the model and the source records | Break-even is defined once, in that function, so the committee, the plant, and the deal team are looking at the same number. New apps reuse what exists and add what they need.