# Konstant Your company is ten to twenty parts in one box. Pricing, scheduling, a review method, a model, a forecast, a check your best people run by hand. Named and taken out one at a time, each becomes something a person, an agent or another company can call. Konstant does the naming with you, carries what your customers said into every move, moves toward the outcome you set and runs the parts in a box you control. A part answers one question, with a number, a range and its limits. Agents propose the parts from the code and its tests; people name them, and the owner decides what a part means and who may use it. Each part gets a typed contract. The expected result of a move is written before it runs and measured after it lands. Arranger tries parts in and out of the live work and measures whether each move brought the outcome closer, using Precise’s mathematics for what each part contributed. A miss rolls back by the owner’s rule. Konstant is the company intelligence product; its agent arrives named Gary and can be renamed. Crossfade puts a change into use with a way back. Boombox is the box the parts run in, hosted by Konstant or in the customer’s own cloud. The network carries a part beyond one company under the owner’s terms. The free start is a parts map: install the kit, point it at a repository, and it returns the parts it found with the question each answers, who would call it, how you would know it was right and what you would build with it first, then stands one up locally with its first test. ## Products and company work - [Home](https://konstant.cloud/) - [Our approach](https://konstant.cloud/approach) - [Konstant company intelligence](https://konstant.cloud/gary) - [Boombox](https://konstant.cloud/boombox) - [Arranger](https://konstant.cloud/arranger) - [Crossfade](https://konstant.cloud/crossfade) - [Engineering notes](https://konstant.cloud/work) - [Operating improvement](https://konstant.cloud/operating-improvement) - [Product expansion](https://konstant.cloud/product-expansion) - [Investment thesis](https://konstant.cloud/thesis) - [Developers](https://konstant.cloud/developers) - [The parts map](https://konstant.cloud/parts-map) - [Contact](https://konstant.cloud/contact) ## Existing references - [Company](https://konstant.cloud/company) - [Authentication](https://konstant.cloud/auth.md) - [OpenAPI](https://konstant.cloud/openapi.json) - [MCP description](https://konstant.cloud/.well-known/mcp.json) - [MCP server](https://konstant.cloud/api/mcp) - [Agent resource catalog](https://konstant.cloud/.well-known/ai-catalog.json) - [Full site text](https://konstant.cloud/llms-full.txt) - [Privacy](https://konstant.cloud/privacy) - [Terms](https://konstant.cloud/terms) # Your company is ten to twenty parts in one box. You own the number. Choose what moves it. Agents are becoming how your customers buy and how your own people work. The software and judgment you already run were built for screens and teams. Konstant takes them out as parts, puts a contract on each and makes them callable, with a defined input, output and revision. Then it aims those parts at what you want: a number to move, a product a customer asked for, a build that used to need a team. [Discuss your first part](/contact) [Get your parts map](/parts-map) Company Kit No. 1 Step 3 Some are code. Some are methods. Some are one person’s judgment. Inside your company first, then for everyone who calls it. [](#why) Company Kit No. 1 Sheet Nine parts on the sprue, one of them a person. Three steps. Snap out before first use. ## Why take them out now. Two problems, one cause. The expertise behind each customer is fused into one product, and none of it has a name. [ ### Every custom request became another codebase. Every codebase became a team. Saying yes to each customer built a product per customer and a payroll to match. ](#bespoke) [ ### The expertise behind each customer already exists. It is trapped in people and fused into products nobody can reach. ](#judgment) [ ### Now agents are becoming how your customers buy. They call the companies that answer in parts. An agent calls a part, not a product: if your pricing, your check or your method has no name and no contract, the agent finds one that does. ](#stack) [ ### The number lives in a few parts. Margin, cost per order, cycle time: each moves with a handful of parts. You cannot move a number you cannot name. ](#outcome) [ ### Named parts are the ones that get paid. What your best people know becomes something another company calls at an exact revision, under your terms, instead of something they rebuild without you. ](#network) ## Keep your stack. Nothing migrates and nothing is rewritten. Konstant reads the software and the working methods you already run, proposes the parts, and your team names them. Each part gets a typed contract where it already lives: input, output, the revision that answered. It runs in a box you control, hosted by Konstant or in your own cloud. The person who owns the number names the parts with the people who know the work. This is a business decision, not work to hand off as tooling. The owner decides what a part means and who may use it. [Where the parts run](/boombox) Sheet Each part has a name, an input, an output and the revision that answers. ## Judgment is a part. Every company has the person who knows which orders are going to be late before anything in the system says so, and has been flagging them for years. The flag is in the system. The reason is in her head. That is judgment, and it is a part. Konstant reads the record of what she marked. Arranger proposes the questions she might be weighing, asks them of every order, and keeps the ones that predict what actually happened. The result is her judgment as six questions she can read and correct, named at a revision with her name on it, and scored against outcomes. It stops leaving at five, and an agent that never met her can call it. [How Arranger works](/arranger) Sheet Her judgment, read from the record: six questions she can confirm or correct, each weighed by how much it predicted what happened. ## Bespoke at scale. Every customer wants something specific, so a company ends up with a codebase per customer, each a monolith nobody wants to touch. Once the parts are named, a new customer need is a new workflow composed from existing parts plus at most one new part. Your agents and the customer’s agents compose the product for the outcome. Sit down with Konstant with your revenue, your roadmap and what customers have been asking for, and design the next product toward the number you want. One-to-one builds, without growing the team. [Build the next product](/product-expansion) Sheet Bespoke at scale: each new need is a new path through the catalog plus at most one new part, composed by your agents and the customer’s. ## Built toward an outcome. Products are designed to have outcomes for the people who use them. AI labs can repeat tests at low cost. In a business loop, every move takes operating time and puts live work at risk. Arranger brings that test-and-measure discipline to the fewest moves to a confident answer, with a person judging each step. Each workflow here is built toward one number: cost per order under twelve dollars, margin up two points, fewer tickets touched by hand. Arranger tries parts in and out of the live work and measures whether each move brought the number closer. The expected result is written before the move; the measured result lands after it; a miss rolls back by your rule. You always know which room you are in: the measured line beside the control, every move marked where a part went in or came out, and the gap that stayed open. When results land, the record moves forward and the next move is chosen from it. Precise’s mathematics measures what each part contributed. Sheet Both lines carry the same weekly noise. After the part goes in, the measured line steps away from the control and holds under the target. The gap that stays open is the contribution. ## Discoverable, and paid. A named part works inside your own workflows first. The owner decides whether it leaves the private catalog: who may learn it exists, who has agreed to what, who may call the exact revision, and what was delivered. The network carries it, and other companies pay you when their agents call your part. Sheet Compute choice is not product lock-in. The part runs where you choose; the terms travel with it. ## How the work runs. Four products, one box. Start with company intelligence or bring existing software to Boombox. ### [Konstant](/gary) #### Aim the work. Konstant finds the work in your company context, including work nobody asks for. It connects what customers say, what people know and the number you want to move. [Company intelligence](/gary) ### [Arranger](/arranger) #### Try parts in and out. Arranger tries parts in and out for the fewest moves to a confident answer. A person judges each step; each result shows what the parts contribute. [Measurement toward the number](/arranger) ### [Crossfade](/crossfade) #### Move the work. Crossfade moves the work with a way back. It connects each change to what happens in use, so people can keep it or return. [Operating change](/crossfade) Beneath all of it ### [Boombox](/boombox) Boombox is the box the parts run in. Each part runs behind a typed contract, hosted by Konstant or in your own cloud. [Bring your code](/developers) ## Konstant in practice. Two companies, two roles. One was read as parts and given moves toward its number. The other made a part that Konstant now calls. Blockdaemon Leadership and board working document · September 2026 ### Monoliths read as parts, with a number to reach. Every institutional customer wanted something specific, and the company had the codebases to show for it. Leadership brought Konstant a revenue target and the record: the CRM warehouse, six months of pipeline, contracts, delivery notes and the conversations behind them. Konstant named the parts of the sales machine that were leaking and found the judgment already working in pockets of the same company: fifteen people practicing rules nobody had written down. The plan named those rules as the company’s, and wrote the moves: repair the sales machine, price bespoke work as a product, expose capabilities to customers’ agents, reprice the installed base. Every move is written before it starts and measured against a control group, so a move gets credit only for what it changed. Each week’s capacity goes to the moves that brought the number closer. The company’s figures, accounts and people stay with the company. One move, as written before it starts Baseline The number today, dated to its source. Expected movement What the move changes, by how much, by when, with a range. Window The weeks it gets to prove it. Stop rule The result that ends it. - Mon Numbers refreshed, one source - Wed Moves chosen, sixty minutes, written memos - Thu to Fri Moves run in the live work - Fri Measured against the control - Monthly Board sees stops, doubles and control results Precise A part another company made ### A part that found a job its maker never planned. Precise develops mathematics for measuring what each part of a result contributed and which move is worth trying next. It runs its own research workloads through Boombox, in its own cloud. Our agents took that part and called it inside Arranger, beside Konstant’s own methods for finding overlooked evidence. Precise never designed it for that. The combination is how Konstant measures every move. Precise keeps its mathematics, its product and its customers. Konstant customers get a maintained part at scale without building it. That is the network in one relationship: one company’s part doing consequential work inside another company’s product. ## Start with a parts map. Free, local, no login. Install the kit and point it at a repository. Your agent interviews you about the outcome, reads the code, the tests and the documentation, and returns a map of the parts it found: the question each answers, who would call it, how you would know it was right, and a place for what you would build with it first. Then it stands up one part behind a typed contract and runs it on your machine with its first test. Nothing leaves the repository until you connect. ``` brew install KonstantCloud/tap/boombox boombox project init . --client claude --client codex ``` Then, in your coding agent: > Map the parts of this repository and stand up the first one.[How the parts map works](/parts-map) ## Start with one part. Bring the number that will not move. Saying yes means Konstant proposes the first part from what you already run, your people confirm it, and it runs in a box you control, hosted by Konstant or in your own cloud. It proves itself against an expected result written before it starts. If your company has no installed base and no number to aim at, this is not for you yet. [Discuss your first part](/contact) # Name the parts. Aim them at a number. Konstant reads the software and methods you already run. Agents propose the parts. Your people name them. Each part gets a typed contract where it already lives, then goes to work on one number you set. [Discuss your first part](/contact) [Get your parts map](/parts-map) ## Read what you already run. Name the parts. Konstant reads your code, your tests and the working methods your people follow. It proposes the parts: the quote, the schedule, the check, the review. Some parts are code. Some are methods. Some are one person’s judgment. ### Name the parts. Read the software, the working methods and what people mark. Propose a name for each useful part. The people who know the work confirm what it means, what goes in and what comes out. Agents propose. People name. The owner decides what a part means and who may use it. A named part carries a typed contract: input, output, and the revision that answered. The contract is what makes the part callable by a person, an agent or another company. ### Judgment is a part. Every company has someone who knows which orders will be late before the system says so. Her read on late orders becomes a part with her name on it, six questions she can read and correct. Sheet Five steps, one box. A part is not in the box until it is named. ## What goes in the box. A company might name parts like these. This is an example list, not a customer result. Specimen 01 Example company parts - 01 Pricing the quote for this order. - 02 Order routing where the order goes next. - 03 Her read on late orders which orders need attention today. - 04 Delivery scheduling the next workable delivery time. - 05 Credit check whether this customer can order on account. - 06 Stock check what is available for this order. - 07 The renewal email the message for this account at renewal. - 08 Exception review what a person needs to check before work continues. - 09 Margin check what remains after the costs of this order. Code, methods and judgment, named one at a time. The list depends on the company. ## One company. A leader has a number to move. The company cannot move it, and the board is watching. A company had a number to move, but could not move it. The board was watching. Its record showed fifteen people practicing rules that no document listed. The parts got named. The moves got written. ## Aim them at one number. Move the work. Every workflow is built toward one number: cost per order under twelve dollars, margin up two points, fewer tickets touched by hand. Konstant holds your revenue, your roadmap and what customers have asked for. Sit down with it to choose the part, the number and the next product. ### Try parts in and out. Arranger adds and removes parts in the live work and measures whether each move brought the number closer. The expected result is written before the move. The measured result lands after it. A miss rolls back by your rule. Precise’s mathematics measures what each part contributed. ### Move the work. Crossfade moves work from a person to a part, or from one workflow to the next, with a scoped transition and a return path. The person reviews what the part is unsure about. ### Run it in a box you control. Boombox is the box the parts run in. It is a private VM hosted by Konstant, or it runs in your own cloud. The terms travel with the part. [Aim the work](/gary) [Try parts in and out](/arranger) [Move the work](/crossfade) [Where the parts run](/boombox) ## Then the network. A named part works inside your own workflows first. The owner decides whether it leaves the private catalog. If it does, another company’s agent can use the exact revision under your terms, and the part gets paid. ### One case, read as parts. At Blockdaemon, every institutional customer wanted something specific, and the company had the codebases to show for it. Leadership brought Konstant a revenue target and the record. Konstant named the parts of the sales machine that were leaking and found judgment already working in pockets of the company: fifteen people practicing rules nobody had written down. Every move was written before it started and measured against a control group. [Read the thesis](/thesis) ## A first engagement. Bring The number that will not move and the people who feel it. Naming the part is the work, not the prerequisite. Work together Konstant proposes the parts from what is already there. Your people confirm them. Hands-on building and integration are part of the scope where needed. Leave with A named part with a typed contract, running in a box you control, with an expected result written before it starts. Commercial scope Agree product access, deployment, ongoing operation and improvement, and any specialist use. Sheet You bring the number on the lid. Konstant proposes the parts. Your people confirm them. ## Start with one part. Bring the number that will not move. We name the first part with you. If your company has no installed base and no number to aim at, this is not for you yet. [Discuss your first part](/contact) # Aim the work. Konstant holds the company context: revenue, roadmap, what customers said, what people marked. Sit down with it to choose the part, the number and the next product. Your agent arrives named Gary. Name it whatever you want. [Discuss your first part](/contact) Sheet Four folders, one bench, one choice. The blue line is the part the number depends on. ## Choose the number. Choose the part. Margin, cost per order, cycle time: each moves with a handful of parts. You cannot move a number you cannot name. Bring Konstant a target and the record, and it shows which parts the number depends on. Konstant reads the software and the methods behind the number and proposes the parts. Your people name them. At Blockdaemon, leadership brought Konstant a revenue target, the CRM warehouse, six months of pipeline, contracts and delivery notes. Konstant named the parts of the sales machine that were leaking. ## Read judgment from the record. Konstant finds the judgment already working in the company. At Blockdaemon it found fifteen people practicing rules nobody had written down. For one person, Konstant reads the record of what she marked. Arranger turns it into a part she can read and correct. ### Find what the priorities miss. A recurring signal can sit outside a declared priority and still matter. Konstant’s selection methods bring overlooked evidence into the room beside the context you asked for: work that is happening that nobody asked for, and work drifting away from the number it was meant to move. ## Design the next product. A new customer need becomes a new workflow: existing parts plus at most one new part. Your agents and the customer’s agents compose it toward the outcome. ### Company context. Company control. Connect the records and systems the work needs. Access follows the person and the source. The company’s figures, accounts and people stay with the company. The owner decides what a part means and who may use it. [One new part per customer need](/product-expansion) [Try parts in and out with Arranger](/arranger) ## Which number do you want to move? Bring the number and one accountable owner. Konstant starts with the parts behind it. [Discuss your first part](/contact) # The box the parts run in. A named part gets a typed contract: input, output, and the revision that answered. Boombox runs it as a product or a capability, hosted by Konstant or in your own cloud. The part keeps its language, its tests and its place. [Discuss your first part](/contact) [Start with your code](/developers) Sheet The box the parts run in. One port lit: a call arrives, the part answers, the rest of the box stays quiet. ## Bring what you have. Bring an application, a repository, a research method or a working process. Keep the expertise that makes it useful. Boombox packages it, deploys it and runs it. The part keeps its language, its tests and its place. ## Your parts. Your choice of cloud. Run in a private VM hosted by Konstant, or deploy in your own cloud. The terms travel with the part. ### Hosted by Konstant A private VM for your company. Konstant provides hosting and ongoing operation. ### In your own cloud Use your company’s cloud environment. Connect the records, services and code the work needs. Agree the environment, the access and the operating responsibilities around the deployment. ## One part. Many callers. A person can use a product surface. An application or an agent can call the part. Arranger can combine it with other parts. The owner decides what the part means and who may use it. Company data stays under the owner’s access decisions. [Combine parts with Arranger](/arranger) ## A part in operation. Precise develops mathematical tools for measuring how the parts of a system contribute to its result. One of its research workloads ran through Boombox in Precise’s own cloud. Boombox kept the result, handled a repeated trigger as the same run and kept the work inspectable after an operator was replaced. Hosted engineering execution recorded July 16, 2026. The record shows operation and recovery of this workload. [Inspect the execution record](/assets/evidence/precise-hosted/manifest.json) ## A local starting point. A second developer example runs Precise’s campaign-analysis software through Boombox. It reads synthetic campaign records and returns a review of planned and reported campaign costs and results. Developers can inspect the inputs, the request and the output. [Inspect the local example](/assets/evidence/precise-local/manifest.json) ## Start directly with Boombox. Install Boombox and connect your coding agent to an existing repository. The install includes the tools, the skills and a local test setup. Describe the result, inspect the code, define the part and run a first test. Connected deployment uses your chosen environment and your authorized access. Commercial scope covers deployment and ongoing operation, plus any specialist use. [Open the developer guide](/developers) ## Which part should run first? Bring the code or the method you already trust. Konstant names the first part with you. [Discuss your first part](/contact) # Try parts in and out. Business work runs once a week with customers in it, so you cannot try everything. Arranger finds the parts worth moving, writes each move before it runs, measures it against a control, and brings you the next two or three moves worth making. [Discuss your first part](/contact) Sheet Both lines carry the same week-to-week noise. After the part goes in, the measured line steps away from the control and holds. The gap that stays open is the contribution. ## Fewer moves, faster answer. A product team can replay a thousand variants overnight. An order desk cannot. Every move on live work costs operating time and carries risk, so Arranger starts with the number, the parts that could change and a budget of moves. The aim is the fewest moves to an answer you can trust, and a stop when the number is credibly met. Two parts that work well alone can disappoint together, so Arranger scores the whole line. ### Konstant’s mathematics finds the candidates. Konstant reads the record behind the number. It measures how parts of the work interact, where a part is drifting from the number, and where work is happening that nobody asked for: orphans. That last kind is where the unlisted part usually hides. Agents propose the moves. People name them. ### Precise’s mathematics scores the result. Once a move has run, Precise’s mathematics assigns the measured change to the parts that changed and measures how parts interact. Two parts that help alone can hurt together, and the number says so before you ship them together. Konstant has published one such case, with the figures. [The published case](/answer-pipeline-evaluation) ## Two or three moves, then you judge. Arranger never runs the whole matrix. It presents the next two or three moves most likely to change the decision, and a person picks. The expected result is written before the move. A miss rolls back by your rule. ### Every move is written first. One move, as written before it starts: Baseline The number today, dated to its source. Expected movement What the move changes, by how much, by when, with a range. Window The weeks it gets to prove it. Stop rule The result that ends it. Once the move is scored, the record shows what was known, what was chosen, what was predicted at what confidence, and what happened. A miss rolls back by your rule. Arranger stops when the number is credibly met or when no remaining move can change the decision. Your existing tests and domain experts supply the measurements and the review. ## Judgment is a part. Arranger ships with judgment discovery built in. Give it the record of what one person marked for years. It proposes the questions she might be weighing, asks them of every order, and keeps the ones that predict what happened. The result is her read on late orders as six questions she can read and correct, named at a revision with her name on it. ### Precise inside Arranger. Precise develops mathematics for measuring what each part of a result contributed and which move is worth trying next. Precise runs its own research workloads through Boombox, in its own cloud. Konstant’s agents called that part inside Arranger, beside Konstant’s own methods for finding overlooked evidence. Precise never designed it for that, and keeps its mathematics, its product and its customers. Konstant customers get a maintained part without building it. ### Keep what the moves taught. Every scored move stays on record: the combination, the prediction, the result. When Crossfade moves the work, what happens in use feeds the next move. [Move the work with Crossfade](/crossfade) ## Which number should move first? Bring the number. Konstant proposes the parts to try first. [Discuss your first part](/contact) # Move the work. Crossfade moves work from a person to a part, or from one workflow to the next. The move has a defined scope, a watch period and a return path. The person reviews what the part is unsure about. [Discuss your first part](/contact) Sheet The handover slider at the halfway point. The tray is in transit; the return path is drawn before the move. ## Scope the move. Every move names four things: the incumbent, the proposed replacement, the affected work and the operating requirements. Where the choice needs evidence first, Switch Check uses Arranger to compare the options and examine failures and interactions. ### The move is written first. Arranger organizes the experiments and the contribution analysis. Crossfade adds the scope and the watch period. The expected result is written before the move and measured in operation against the work it replaced. ## Three steps. Understand the move Bring the number, the current setup, the proposed part and the evidence you have. Define right with the people who own the result. Make the move Identify the work the part takes on, what must stay compatible, and how work already underway finishes. Watch and respond Tie each result to the setup that produced it. Keep the part, investigate further, or return by the owner’s rule. ### You keep the decisions. You keep your application, your private data, your quality standards and your release decisions. Boombox is the box the part runs in, and the part stays callable by the people and agents you allow. The return path states what can be restored. [Try parts in and out with Arranger](/arranger) ## Which workflow should move first? Bring one workflow. Konstant proposes the part that takes it on. The engagement defines what runs, who owns it, how to judge the effect and how to return. [Discuss your first part](/contact) # Engineering notes. Implementation and internal evaluation records, with inputs, outputs and the limits of each result. ## Answer-pipeline attribution. Precise develops mathematical methods for measuring what the parts of a system contribute and how they interact. We used those methods in an internal evaluation of how filtering and compact formatting affect Konstant’s answers. The record contains four measured configurations, the computed contributions and the development decision. The measurements concern answer coverage in a limited comparison. They do not establish a customer or financial outcome. [Read the technical note ↗ ](/answer-pipeline-evaluation) ## A hosted capability execution. Boombox also ran a Precise research workload in Precise’s own cloud. This separate execution demonstrates retaining a result, handling repeated triggers and making the work available to a replacement operator. [Inspect the execution record ↗ ](/boombox#hosted-run) ## Selecting a next experiment. Precise also supplies a method for choosing which experiment to run next and when to stop. We connected it to Arranger in a study using illustrative probabilities. You can inspect the inputs and the returned recommendation. [Inspect the method integration ↗ ](/assets/evidence/konstant-precise/arranger-study.json) ## Build with the developer kit. Bring an existing method or repository and define the first useful result. The developer guide provides a tested local starting point and explains the access needed for connected operation. [Open the developer guide ↗ ](/developers) # Move one operating number. Cost per order. Margin. Cycle time. Each moves with a handful of parts. Konstant finds them, your people name them, and every move is measured against a control. [Discuss your first part](/contact) ## Start where it hurts. A costly exception, a slow handoff, a constrained line. Pick one. Konstant reads the code, the methods and the record behind it and proposes the parts. ### The part that is a person. Every company has the person who knows which orders will be late before anything in the system says so. The flag is in the system. The reason is in her head. Konstant reads the record of what she marked. Arranger turns it into six questions she can read and correct, named at a revision with her name on it. It stops leaving at five, and an agent that never met her can call it. Sheet The late order flag. The clip catches the card that would have been late; the needle is the number moving. ## Try parts in and out. Move the work. Arranger tries parts in and out of the live work and measures whether each move brought the number closer. Judge the whole line against the operating objective. A faster step counts when it helps the customer or the business result. Include quality and exceptions. ### Move the work. Crossfade moves the work from a person to a part, or from one workflow to the next, with a scoped transition and a return path. The person reviews what the part is unsure about. The operating owner and domain experts stay responsible for how the work is used and judged. ### Tie the move to the economics. Finance connects observed changes to business value. Released hours create capacity. Realized savings, or profitable use of that capacity, need their own evidence. Keep the corrected assumptions and the results for the next move. [Develop a new customer offer](/product-expansion) ## Which number do you want to move? Bring the number and one accountable operating owner. [Discuss your first part](/contact) # Build the next product from parts you already have. Every customer wants something specific. Once your parts are named, a new customer need is a new workflow composed from existing parts plus at most one new part. [Discuss your first part](/contact) ## Why every yes became a codebase. Each custom request became another codebase. Each codebase became a team. The expertise behind each customer already exists. It is trapped in people and fused into products nobody can reach. ### Name the parts first. Konstant reads your software and your methods and proposes the parts. Your people name them. Each part gets a typed contract where it already lives. Sheet One need, one new part. The path runs through what is already in the box; only the last cell is new. ## Compose the product toward an outcome. Sit down with Konstant, with your revenue, your roadmap and what customers have been asking for. Design the next product toward the number you want. Konstant finds the accounts that kept asking. Offer the product to half of them; the other half is the control. Your agents and the customer’s agents compose it from existing parts plus at most one new part. Arranger tries parts in and out and measures what each contributed. ### Run it where the customer works. Boombox runs the parts as a product or a capability, in a private VM hosted by Konstant or in your own cloud. The customer brings the context and access the result needs. Your company keeps its method, its standards and its relationship. ## Then let the parts get paid. A named part works inside your own workflows first. The owner decides whether it leaves the private catalog: who may learn it exists, who may call the exact revision, and what was delivered. The network carries it. That is how a company is paid for its expertise by other companies’ agents. [Read the thesis](/thesis) ## What does your next customer need? Bring the request you keep saying yes to. We find the parts behind it. [Discuss your first part](/contact) # The thesis. The model is the new means of production. What a model works on is where the value stays. Konstant is built so that stays with the company. ## The change. The model is the new means of production. The labs that build models are becoming software companies. They will ship products that do the work of whole departments, host the service, and take a piece of what the work earns. The offer is convenient. The terms are permanent. A general product does general work. It is built for everyone, so it is fitted to no one. What it can do for a company is limited by what the company hands it, and what a company hands it does not stay the company’s. ## The company town. A company that rents its operations from a platform lives in a company town. The platform sets the prices, keeps the records, and watches the business. The knowledge of its best people becomes training data. What makes the company different becomes a feature every tenant shares. No one wants to work in a company town. ## The alternative. The alternative is not refusing the models. It is owning what they work on. A company’s expertise already exists. It sits in code, in methods, and in the judgment of the people who have been there longest. Named and given contracts, that expertise becomes parts the company owns: the quote, the schedule, the credit check, her read on late orders. Each part runs in a box the company controls, and each answers a call, from a person, from an agent, from another company on the company’s own terms. The labs supply the intelligence. The parts are the company. Models will keep improving, and they will stay interchangeable. What a model works on is where the value stays. - 04 Her read on late orders judgment One part. A contract on it. A box the company controls. ## What Konstant is. Konstant is an AI lab you own. We read the software and the working methods a company already runs, propose the parts, and name them with the people who know them. Each part gets a typed contract and runs in a box the company controls, hosted by us or in the company’s own cloud. The parts are aimed at a number the company sets. Every move is written before it starts and measured after it lands. This is not a prediction we are waiting on. At Blockdaemon, every institutional customer wanted something specific, and the company had the codebases to show for it. Read as parts, the same company found the moves: repair the sales machine, price bespoke work as a product, re-price the installed base. The method works because the expertise was already there. It always is. A leader has a number to move. The company cannot move it, and the board is watching. A company had a number to move, but could not move it. The board was watching. Its record showed fifteen people practicing rules that no document listed. The parts got named. The moves got written. ### The assets stay with the company. A company’s methods, software, private learning and customer relationships remain the company’s. Access and commercial terms decide how a part is used and which results may travel. Joining the work does not mean handing private context to every provider. ## What happens next. More becomes possible between companies. When parts have names and contracts, they can be called. A customer may need a method its supplier already owns. A partner may add a capability that makes a product more useful. A company’s agent may find that need while working on a real question. Named parts make that expertise discoverable and usable under the owner’s terms, and each company can draw on the network and supply to it. This already runs. Precise develops mathematics for measuring what each part contributes to a result. Our agents called that part inside Arranger, beside Konstant’s own methods for finding overlooked evidence, for a use Precise never designed it for. One company’s part, doing consequential work inside another company’s product. A company that names its parts first keeps its expertise through the change, and gets paid for it after: its parts answer other companies’ agents at an exact revision, under its terms, instead of watching its methods rebuilt without it. The platforms will offer the convenient version. We are building the owned one. ## Begin with useful work. Bring one consequential business decision: an opportunity for new revenue, a costly operating problem, or a choice between capabilities. The first engagement names the first parts and aims them at that number. What happens next follows the work. [Discuss your first part](/contact) # Already have the code? Start there. Install Boombox, connect your coding agent to an existing repository and stand up your first part. ## Install Boombox. One installation includes the CLI, TypeScript SDK, agent skills, schemas and a local test setup. It includes its own runtime, so you do not need to install Node, npm or Rust separately. On macOS or Linux with Homebrew: ``` brew install KonstantCloud/tap/boombox ``` Or use the macOS/Linux installer: ``` curl -fsSL https://github.com/KonstantCloud/boombox/releases/latest/download/install.sh | sh ``` Windows archives and Debian/Ubuntu packages are available from the [official releases](https://github.com/KonstantCloud/boombox/releases/latest) . Keep the complete installation together. ## Connect your coding agent. From your existing project directory: ``` boombox project init . --client claude --client codex --json boombox tree boombox docs agents ``` Initialization adds the build-on-boombox skill and a credential-free local MCP connection for the selected agents, and returns the exact connection commands for the project. Reload your coding agent, then ask: > Use build-on-boombox to inspect this codebase and build the smallest working Product slice. Keep our language and existing tests. Prove it locally, then use our authorized account for any connected work. The agent inspects the repository, proposes the parts and tests the first one locally without a Boombox login. Initialization does not upload the repository or deploy an application. Real output of project init on a fresh repository with the complete installation and no login. Three connections are printed. Only the credential-free scan is registered. ## Connect the account the work needs. When a part needs company capabilities, data or deployment, run boombox login --account. Sign in and choose an authorized Product account by company name. Use the connection and available targets returned for that account. The optional builder workspace uses boombox login. It carries project continuity, requests for missing platform capabilities and evaluation facts. Product-account access remains a separate connection. project init returns the corresponding MCP commands. Register the appropriate connected command after login; only the local scan connection is registered automatically. [Authentication and account access ↗ ](/auth.md) ## Keep your language. Name the part. Your application keeps its implementation language, runtime, build tools, existing tests and deployment requirements. Use the account’s published contracts to connect parts to the work. Applications call parts over HTTP or the SDK directly, not through the CLI per request. If your application imports the TypeScript SDK or you choose npm distribution, pin the package exactly: npm install --save-dev --save-exact --ignore-scripts @konstantdotcloud/boombox. Pin the exact version listed in the [release notes](https://github.com/KonstantCloud/boombox/releases/latest) , then run node ./node_modules/@konstantdotcloud/boombox/dist/boombox.js project init . --client claude --client codex --json. Keep that dependency and lockfile; do not use unpinned npx. boombox tree shows the installed tools. boombox docs agents opens the agent guide. boombox paths --json locates the bundled SDK, schemas and test fixtures. A first useful result is a working local part or an application deployed to an authorized target. Judge it by what someone can use. ## Keep going. [Boombox installation and guide Official release ](https://github.com/KonstantCloud/boombox/releases/latest) [Homebrew installation Official tap ](https://github.com/KonstantCloud/homebrew-tap) [Boombox Account sign-in ](https://boombox.konstant.cloud) [Konstant API description OpenAPI ](/openapi.json) [Machine-readable site map Text ](/llms.txt) [Authentication reference Markdown ](/auth.md) ## Put one part into use. A recurring decision. A method you already trust. An application with somewhere new to go. [Discuss your first part](/contact) # The parts map. One page listing the parts of your company found in a repository: the question each answers, who would call it, how you know it was right, and what you would build with it first. It starts with an interview about the outcome. Free, local, no login. [Install the kit](/developers) ## Four questions per part. Question The one question this part answers. Proposed from the code and its tests. Confirmed by the owner. Caller Who would call it: a person, an agent, a workflow, another company. Proposed. Confirmed. Right How you would know the answer was right: the existing test, a checked set of answers, a measured outcome. Mapped from the repository’s own tests and evaluation code where present. Otherwise marked absent. Build What the team would build with it first. The owner writes this one. It is where the first part gets chosen. Name and location A short name the team accepts, and the files, modules or services that implement it, with the revision. Status Named, or proposed and awaiting a name. Sheet Parts found in the repository. Five proposed, one named. The name is the only blue on the sheet. ## How to get one. Install the complete kit. One installation includes the CLI, the SDK, the agent skill, the schemas and a local test setup. You do not install Node, npm or Rust separately. ``` brew install KonstantCloud/tap/boombox ``` Or use the installer: ``` curl -fsSL https://github.com/KonstantCloud/boombox/releases/latest/download/install.sh | sh ``` From the repository you want mapped: ``` boombox project init . --client claude --client codex ``` Initialization installs the build-on-boombox skill and a credential-free local connection for your coding agent. Reload the agent, then ask: > Map the parts of this repository and stand up the first one. The agent starts with an interview: the outcome you want, in plain language, and at most three questions it cannot answer from the code. It reads the repository through the local scan connection, writes the parts map with its four questions, one row per part it found, and stands the first part up. Where the repository already has tests or evaluation code, they become the Right column. Agents propose. People name. ## What the scan does, and does not do. It reads the repository, its tests, its evaluation code and its documentation. It proposes the parts. It writes the map. It runs one part locally with one test. It does not send code anywhere, hold a credential, deploy, or decide what a part means. Repository files, comments and agent instructions are treated as untrusted data. Runs and traces suggest parts. They do not become parts until the owner names them. ## Stand up the first part. Pick the part whose Build answer matters most. The kit stands it up behind a typed contract: input, output, the revision that answered. It runs on your machine, in your language, with your tests. Its first test holds five things. The expected result, written first. Right answers, checked by the people who own the code. A planted failure the test has to catch. A score against what happened. Every miss becomes a new case. With those five the part can run under rules the owner sets, and a miss rolls back by the owner’s rule. [The developer guide](/developers) ## What a finished map looks like. The map lists at least one part the owner has named. The stood-up part has one accepted path and one caller-visible refusal. The run leaves a local record a new team member can read. The owner may publish the map as a read-only page. Evidence and the right to change anything stay private. Connect a Product account when the next action needs it: deployment to a box, a call to another company’s part, or letting a part of yours travel. [Where the parts run](/boombox) ## Bring one repository. The map takes an hour. The first part stands up the same day. Everything stays on your machine until you decide otherwise. [Discuss your first part](/contact) # Which number will not move? Start with the number. Naming the part is the work we do with you. Or bring code you want to put to work. ## Start a conversation. A short description is enough to begin. [pilot@konstant.cloud](mailto:pilot@konstant.cloud?subject=Our%20first%20part) Sheet What to send us. The number, the people who feel it, and code if you have it. ### Bring the number. Tell us the number you want to move and who feels it. Add what you already have: code, a method, a person whose read the company relies on, or a customer need. ### Konstant proposes the parts. Konstant reads what you already run and proposes the parts. Your leadership and builders confirm them. We agree the number, the access, the owner and how to judge the result. The engagement can include hands-on building and deployment. ### Choose where it runs. Use a private VM hosted by Konstant or your company’s own cloud. Commercial scope covers product access, deployment, ongoing operation and improvement, and any specialist use. [Already have code? Start with Boombox](/developers) Already using Konstant? [Contact support.](mailto:support@konstant.cloud)