Arsum

What it does

Writes code

YesCustom application and back-end code is written by Arsum's engineers as part of a scoped build, covering interface, back-end and model integration together.Scope the interface, back-end, model integration and required system connections together.arsum.com/services/ai-products-applicat… ↗

Debugs and fixes

PartlySupport and incident response on a live AI system is one of four named engagement types, but it is scoped per contract and the vendor explicitly declines to promise a managed-operation service or response time.This page does not promise an established managed-operation service, a response-time guarantee, or a measured client outcome.arsum.com/ai-integration-services ↗

Writes tests

YesAcceptance testing against representative examples and failure cases is part of the build scope, including permissions, invalid inputs and recovery paths.Use representative examples and failure cases to agree on acceptance. Include permissions, invalid inputs, approval steps, cost limits and recovery…arsum.com/services/ai-products-applicat… ↗

Ships it

YesDeployment is inside the engagement rather than left to the client, and the handover step names the deployment environment and rollback explicitly.Define the deployment environment, code and account ownership, documentation, rollback and support boundary.arsum.com/services/ai-products-applicat… ↗

Done-for-you service

YesArsum is a delivery studio, not software you license: its people scope, build, deploy and then hand over the system, with support scoped separately.Arsum scopes and builds production AI applications, intelligent search systems, and AI integrations. We connect the data, test real cases, deploy the…arsum.com ↗

Not established: Reviews code, Whole-codebase work

How much it does unattended

Runs autonomously

NoThe delivered pattern deliberately keeps a person in the loop: the system prepares output and a named human approves release, which Arsum states as a design boundary.The new application automates that preparation, but it does not give the model ownership of the final release. A practitioner reviews the generated…arsum.com/case-studies/attuned-health ↗

Agent permissions

PartlyPermission boundaries are a design decision Arsum settles per engagement rather than a fixed product default, deciding where approval is required before action.Decide whether the system may draft, recommend, or act, and which actions require approval.arsum.com/ai-integration-services ↗

Which models it runs on

Claude

PartlyAnthropic models appear in the published implementation stack of one delivered client build, which shows Arsum works with Claude but is not a product-wide support statement.AI workflow OpenAI · Anthropicarsum.com/case-studies/attuned-health ↗

GPT

PartlyOpenAI models are named in the same delivered stack, evidencing hands-on GPT work on a client engagement rather than a supported-model list across all projects.AI workflow OpenAI · Anthropicarsum.com/case-studies/attuned-health ↗

Model choice

PartlyModel choice sits with Arsum's architecture work and is expected to change over time; two different providers appear in delivered work, so the client is not locked to one vendor.A production system must survive real data, permissions, exceptions, changing models, and real users.arsum.com ↗

Not established: Open models

Whose machine it runs on

Self-hosted

PartlyThe system Arsum builds runs in an environment the client owns, with code and account ownership settled at handover, but there is no Arsum platform to self-host.Define the deployment environment, code and account ownership, documentation, rollback and support boundary.arsum.com/services/ai-products-applicat… ↗

Not established: Open source

What it costs to run

How it meters

YesPricing is per scoped engagement with a published target range, and third-party model, hosting and support spend is estimated on top rather than bundled.Our target for an initial scoped engagement is USD $5,000–$20,000, with longer projects possible. ... Model usage, hosting and ongoing support are…arsum.com/services/ai-products-applicat… ↗

Free tier

NoThere is nothing to sign up for: engagement begins with a project brief and a call that decides whether any project happens at all.The first call identifies whether the next step is discovery, a scoped build, an integration, support, or no project.arsum.com ↗

Bring your own key

PartlyInference and hosting are quoted as the client's own explicit costs rather than resold by Arsum, which implies client-held provider accounts, though keys are never discussed directly.Model usage, hosting and ongoing support are estimated explicitly.arsum.com/services/ai-products-applicat… ↗

Buying it for a team

A company can buy it

YesThe buyer is a company: Arsum addresses founders, product and technology leaders and asks for the person who can accept the work.Arsum works with founders, product leaders, CTOs, and functional owners who need an AI product or workflow to perform in the real world.arsum.com/about ↗

Admin controls

PartlyAccess control is designed into the systems Arsum builds, applying the user's own access rules before data reaches a result or the model, but no Arsum admin console is offered.Apply the user’s access rules before information enters a result or model context.arsum.com/services/intelligent-search-d… ↗

Audit log

PartlyAudit records are named as something specified during an integration's exception planning, so they are scoped work rather than a standing feature a buyer gets.Specify retries, escalation, audit records, rollback, and what happens when a source or model is unavailable.arsum.com/ai-integration-services ↗

Not established: Single sign-on

What happens to your code

Data residency

PartlyArsum LLC is a United States entity in Wyoming and reserves the right to process data outside the country of collection, with no jurisdiction choice offered to buyers.Arsum and its service providers may process information in countries other than the one where it was collected. Where required, we use appropriate…arsum.com/privacy ↗

Getting out

YesExit is a defined deliverable: code and account ownership, documentation, rollback and the support boundary are settled at handover rather than left open.Define the deployment environment, code and account ownership, documentation, rollback and support boundary. Launch acceptance and later feature…arsum.com/services/ai-products-applicat… ↗

Not established: Opt out of training, Certifications