Blueprint

How Specc is built.

Specc builds and runs your integrations as versioned specifications. Each specification defines how data moves, how it changes and what should happen along the way. You can inspect the definition, follow execution results and control changes as your systems evolve.

Integration
The systems, data and outcome you want to connect.
Specification
The versioned definition of how the integration works.
Run
One execution of a selected specification version.
Record
An item of data whose processing and delivery outcomes you can follow.

Describe the outcome. Specc builds the integration.

Tell Specc which systems you want to connect and what you want to achieve. The builder works through API documentation, authentication, data structures and mapping. It creates the specification and uses testing and execution results to refine the implementation.

The technical work becomes something you can inspect: the requests, transformations, conditions and settings that make your integration work.

AI builds and investigates. The runtime follows the specification.

Specc uses AI to build integrations, explain their behavior and investigate problems. A dedicated runtime executes the selected specification using its defined operations and rules.

Once deployed, an integration runs independently of the builder conversation. Its behavior follows the deployed version, giving you a stable definition to inspect, test and maintain.

From your intent to a running integration
  1. BuildAI builderCreates and refines the definition.
  2. ReviewSpecificationA version you can inspect and deploy.
  3. RunRuntimeExecutes the defined operations.
  4. ObserveYour systemsRequests, responses and outcomes.

One specification defines the work.

A specification brings together the parts of an integration:

Triggers
Start work on a schedule, through a webhook or from an incoming email.
Connections
Define access to supported APIs and databases.
Transformations
Map, filter, match, join and reshape data.
Conditions and loops
Route work and process collections.
State and effect records
Track progress and previously completed operations.
Variables
Adapt the integration to a customer or environment.
Review steps
Let people approve selected work before execution continues.

Authentication credentials are managed separately. The specification describes how to use a connection without containing its secret values.

Follow data from source to destination.

Consider an integration that turns orders into invoices. A trigger starts the run, Specc retrieves the orders, matches customer references and maps the required invoice fields. The runtime then sends the requests to the accounting system and records their outcomes.

Example journey · Orders to invoices

  1. Retrieve orders
  2. Match customers
  3. Map invoice fields
  4. Send and record outcomes

Activity brings together run status, delivery outcomes and available execution details. You can inspect requests and responses, review transformed data and identify where work needs attention.

Recovery builds on what already happened.

Specc keeps execution evidence and a durable record of tracked writes. When an operation uses an explicit effect key, a confirmed successful write can be reused during recovery, preserving its result for later steps.

Failures remain visible with their context. If the destination's response leaves a write uncertain, Specc records that uncertainty and prevents a blind retry under the applicable effect policy. You can investigate the outcome and choose the appropriate recovery action.

Retries follow the integration's configured rules and the evidence available for the affected work.

Keep integrations working as systems change.

Enable Self heal to help investigate execution problems. It examines recorded failures, groups related issues and prepares an explanation and proposed next steps.

A proposal may update the specification or identify an action such as renewing access or correcting source data. You review the explanation and decide whether to apply it. After the fix, you can separately select eligible work to retry and inspect the results.

  1. Understand the issueReview the investigation and proposed next steps.
  2. Choose the changeDecide whether to apply the proposed fix.
  3. Review the recoverySeparately select eligible work to retry and inspect its results.

Control the version that runs.

Changes create new specification versions, preserving earlier definitions. You choose when to deploy a version, and execution records identify the version used.

An earlier supported version can be selected for a new deployment when its validation and connection requirements are satisfied. Version history gives you a concrete basis for reviewing changes and understanding past behavior.

Reuse your work across customers.

Create a reusable integration and install it for different customers. Each installation has its own definition, configuration and execution history, with access governed by its workspace and client permissions.

Customer-specific variables and connection settings let you adapt the integration while reusing the implementation you have already built.

Access the integration through the app or API.

Use the app to build, configure and inspect integrations. The authenticated API also lets your own tools retrieve specification JSON, start runs and read execution results.

Keep access and credentials under control.

Specc applies workspace and client access controls to integrations and their execution data. Authentication credentials are stored encrypted and kept separate from specification documents. Execution evidence uses defined redaction and retention policies.

Specc is operated from Norway. The core V2 application is hosted on Google Cloud in Finland.

Built for ongoing operation

Build the connection.
Keep control as it grows.

From the first specification to ongoing operation, Specc brings implementation, execution visibility and maintenance into one workflow.