Ellipse Gradient for Header

Martini vs SAP Integration Suite

Which enterprise integration platform fits your architecture?

Quick Verdict

Martini and SAP Integration Suite are enterprise integration platforms for connecting applications, APIs, data, messages, events, trading partners, and business processes across cloud and on-premises environments.

Martini is designed primarily for enterprise developers who want low-code productivity without giving up Git, Java libraries, custom code, native REST and GraphQL API development, event-driven architecture, or control over where the complete runtime executes.

SAP Integration Suite is SAP's strategic integration platform on SAP Business Technology Platform. It combines Cloud Integration, API Management, API Composition, Event Mesh, Advanced Event Mesh, Open Connectors, Trading Partner Management, Integration Advisor, Integration Assessment, Migration Assessment, Edge Integration Cell, AI-assisted development, and thousands of prebuilt SAP and third-party integration assets.

Consider Martini when

You want integration and API development to operate like part of your conventional software-development stack.

  • Build REST and GraphQL APIs, integrations, workflows, event-driven services, and backend processes in one environment.
  • Use visual development while retaining direct access to Groovy, Java classes, arbitrary JAR files, Spring libraries, custom functions, and scripts.
  • Manage Martini packages directly through Git branches, pull requests, tags, and conventional CI/CD pipelines.
  • Deploy the complete Martini Runtime in Lonti-managed infrastructure, your own cloud account, or on-premises.
  • Use REST, GraphQL, SOAP, AsyncAPI, databases, files, webhooks, and message brokers as first-class integration building blocks.
  • Connect to APIs and applications without connector-specific licensing fees.
  • Use published transaction pricing with fixed-price unlimited-transaction plans available for higher-volume workloads.

Consider SAP Integration Suite when

You want a broad enterprise integration platform with particularly deep SAP connectivity, B2B capabilities, eventing, API governance, and SAP-specific migration and integration tooling.

  • Use more than 3,400 prebuilt integrations and accelerators for SAP, third-party, and government applications.
  • Build A2A, B2B, and B2G integrations using Cloud Integration.
  • Use dedicated SAP adapters for S/4HANA, IDoc, RFC, OData, XI, SuccessFactors, Ariba, and other SAP systems.
  • Use API Management with gateway policies, Developer Hub, API products, subscriptions, traffic management, and lifecycle governance.
  • Expose SAP business data through API Composition using OData V4 or GraphQL.
  • Use Trading Partner Management and Integration Advisor for EDI and B2B integration.
  • Build event-driven architectures using Event Mesh or Advanced Event Mesh.
  • Use Edge Integration Cell to execute integration flows and APIs inside customer-controlled Kubernetes infrastructure.
  • Use direct GitHub integration together with SAP transport-management and CI/CD capabilities.
  • Use AI-generated integration flows, flow-step recommendations, script optimization, AI-assisted error resolution, and API analytics.

SAP Integration Suite is particularly broad for organisations with substantial SAP estates because many capabilities address SAP-specific application, B2B, event, API, and migration requirements.

Martini vs SAP Integration Suite at a Glance

DimensionMartiniSAP Integration Suite
Product orientationDeveloper-centric integration, API, workflow, and backend automation platformEnterprise iPaaS for SAP and non-SAP integration, APIs, B2B, events, and hybrid integration
Primary development modelVisual low-code + pro-codeVisual integration flows + adapters + mappings + scripts
Typical userEnterprise developer, integration developer, solution architectSAP integration developer, integration architect, enterprise middleware team
Major strengthDeveloper control, Java extensibility, native API development, runtime portability, and simpler commercial modelSAP ecosystem depth, prebuilt content, B2B, API management, and hybrid integration
Prebuilt integration contentMarketplace packages plus open standards3,400+ prebuilt integrations and accelerators advertised
REST API developmentYesYes
GraphQL API consumptionYesPossible through HTTP and API integration patterns
GraphQL API exposureNative arbitrary GraphQL APIsGraphQL access to business data graphs through API Composition
General-purpose GraphQL schema/resolver developmentYesNo equivalent general custom GraphQL server-authoring model identified
Customer-hosted runtimeComplete Martini RuntimeEdge Integration Cell for supported integration and API workloads
Cloud design/control plane required for hybrid runtimeDepends on selected Martini deployment architectureYes; Edge integration content is designed and centrally managed through SAP Integration Suite
GitStandard Git workflowDirect GitHub integration for Cloud Integration plus SAP transport tooling
Commercial modelTransaction allowance or unlimited-transaction plansEdition subscription plus message entitlement and optional add-ons

SAP Integration Suite is substantially broader than a simple Cloud Integration comparison. The platform combines application integration, API management, semantic API composition, eventing, B2B partner management, EDI design assistance, SAP migration tooling, third-party connectors, and hybrid runtime capabilities.

Martini is more focused on developer-led application integration and backend services. Its architecture combines visual integration with native API development, Java extensibility, Git, messaging, databases, events, and deployable application runtimes.

Integration and Workflow Development

CapabilityMartiniSAP Integration Suite
Visual workflow / integration-flow designerYesYes
RoutingYesYes
Conditional logicYesYes
Split / gatherYesYes
Parallel processingYesYes
Reusable subprocessesYesYes, local integration processes and ProcessDirect patterns
Exception handlingYesYes
Transaction handlingYesYes
Scheduled integrationYesYes
Webhook / HTTP-triggered integrationYesYes
Visual mappingYesYes
Message mappingsYesYes
XML / XSLTYesYes
Database integrationYesYes
File / SFTP integrationYesYes
JMSYesYes
KafkaYesYes
AMQPYesYes
Event-driven processingYesYes
Persistent retry queuesYesYes through JMS and related patterns

SAP Cloud Integration models integrations as integration flows, commonly called iFlows. An iFlow combines sender and receiver adapters, mappings, routing, transformation, scripts, persistence, subprocesses, security, exception handling, and messaging patterns.

SAP provides specialised adapters for many SAP technologies as well as common enterprise protocols and third-party services. This is particularly valuable when a large proportion of the integration estate involves SAP applications.

Martini workflows use a similar visual orchestration approach but workflows operate alongside reusable services, APIs, database services, functions, Java classes, event endpoints, and other normal project assets.

APIs and Connectivity

CapabilityMartiniSAP Integration Suite
Consume REST APIsYesYes
Consume SOAP servicesYesYes
Consume ODataYesYes
Consume GraphQL APIsYesPossible through HTTP/API integration patterns
Consume AsyncAPI definitionsYesNo equivalent first-class AsyncAPI import workflow identified in current documentation
Create REST APIsYesYes
Create SOAP APIsSupportedYes
Create OData APIsSupported through Martini API/data capabilitiesYes
Native arbitrary GraphQL APIsYesNo equivalent general-purpose schema/resolver development model identified
GraphQL business-data APICan build custom GraphQL APIs over arbitrary services and dataYes through API Composition business data graphs
API gatewayAPI publishing, security, and managementYes
Developer portal / hubAPI documentation capabilitiesYes, Developer Hub
API products and subscriptionsSupported through API architectureYes
Rate limits / quotasSupportedYes
IP filteringSupportedYes
Threat protectionSecurity controlsJSON and XML threat-protection policies
Custom adapters / connectorsYesYes
Open ConnectorsNot a separate Martini licensing conceptDedicated third-party SaaS connectivity capability

SAP API Management provides dedicated API design, proxying, security, traffic management, lifecycle governance, analytics, subscriptions, and Developer Hub capabilities.

SAP's API Composition capability adds a distinctive semantic-data feature. Business data from supported SAP systems and extensions can be exposed as a unified business data graph and queried using OData V4 or GraphQL.

This GraphQL capability should be distinguished from general-purpose GraphQL backend development. API Composition exposes a semantic business data graph; Martini allows developers to build arbitrary GraphQL schemas, queries, mutations, subscriptions, and resolvers backed by custom services and code.

SAP's Open Connectors capability adds packaged connectivity to third-party SaaS products through normalised REST APIs and authentication models.

Extensibility and Custom Development

CapabilityMartiniSAP Integration Suite
Groovy scriptsYesYes
Java-based script capabilityJava classes and Java ecosystem directlyJava script steps are supported within SAP Cloud Integration constraints
JavaScriptYesSupported in applicable integration/runtime capabilities
Direct Java classes in normal project logicYesMore constrained than Martini's general application-runtime model
Arbitrary JAR dependenciesYesNot equivalent to unrestricted application-level JAR reuse
Spring-library reuseYesNo equivalent general-purpose Spring project model identified
Custom adaptersYesYes
Adapter SDK / developmentMartini Java/package extensibilityCustom adapters can be developed using SAP adapter-development tooling
External custom servicesYesYes
Reusable scriptsYesYes, Script Collections
Reusable mappingsYesYes

SAP Integration Suite provides meaningful pro-code extensibility. Cloud Integration supports Groovy and Java script steps, reusable Script Collections, custom integration adapters, external APIs, and extensive adapter configuration.

SAP's guidance nevertheless recommends using supported APIs and libraries inside scripts because integrations can become fragile when they depend on internal or unsupported runtime classes.

Martini exposes a more general JVM application environment. Developers can directly use Java classes, arbitrary JAR files, Spring libraries, Groovy services, custom functions, and script nodes in the same project as integrations and APIs.

B2B and Trading Partner Integration

CapabilityMartiniSAP Integration Suite
B2B integrationYesYes
EDI processingCan be implemented through integration componentsDedicated capability
Trading-partner managementCan be modelled in applications/workflowsDedicated Trading Partner Management
Partner agreementsCan be builtDedicated first-party model
AS2Supported through relevant integration/protocol componentsYes
SFTP / FTPYesYes
EDI standardsCan process structured formatsDedicated libraries and Integration Advisor type systems
AI-assisted B2B mappingAI-assisted mapping directionYes through Integration Advisor
Message implementation guidelinesCan model transformationsDedicated MIG capability
Mapping guidelinesMappingsDedicated MAG capability

SAP has a significant advantage for organisations with large B2B integration programmes. Trading Partner Management provides dedicated modelling and governance of companies, trading partners, agreement templates, agreements, protocols, and partner-specific configurations.

Integration Advisor adds message implementation guidelines and mapping guidelines based on standard B2B type systems and uses machine-learning-assisted recommendations to accelerate integration design.

Development Lifecycle

CapabilityMartiniSAP Integration Suite
Git integrationYesYes
Direct GitHub repository integrationYesYes
Import artifacts from branchStandard Git workflowYes
Push artifacts to branchStandard Git workflowYes
Pull artifacts from branchStandard Git workflowYes
Native direct GitLab integrationYes through standard GitNo equivalent direct Cloud Integration integration identified in current Git Access documentation
Native direct Bitbucket integrationYes through standard GitNo equivalent direct Cloud Integration integration identified in current Git Access documentation
BranchesYesYes through configured GitHub repositories
Pull requestsNormal Git-provider workflowCan be performed through GitHub around pushed integration artifacts
Built-in artifact version historyGit and package versioningYes
Revert artifact versionYesYes
DEV / TEST / PRODYesYes
Manual package export/importYesYes
Cloud Transport ManagementNot requiredYes; included with Enhanced according to current pricing
CI/CD automationStandard Git CI/CDYes through GitHub integration, APIs, SAP transport tooling, and external CI/CD

SAP's current Cloud Integration Git Access directly integrates GitHub into the integration-content lifecycle. Administrators can register repositories, and integration developers can import, push, and pull artifacts against selected branches.

This significantly strengthens SAP Integration Suite's conventional software-development workflow compared with older versions of the platform that relied more heavily on internal versions and transport mechanisms.

SAP also retains platform-specific lifecycle mechanisms. Integration artifacts have their own version history, packages can be transported between tenants, and SAP Cloud Transport Management can automate controlled promotion through landscapes.

Martini remains more repository-centric because Martini packages are conventional Git-managed development projects rather than cloud-platform artifacts that can additionally be synchronized with a repository.

Deployment and Infrastructure

Deployment requirementMartiniSAP Integration Suite
Vendor-managed cloud runtimeYesYes
Customer-managed integration runtimeYesYes, Edge Integration Cell
Private-cloud executionYesYes
On-premises executionYesYes
Kubernetes runtimeSupported through customer deployment architectureYes, required for Edge Integration Cell
Customer controls runtime computeYesYes for Edge Integration Cell
Customer provides production databaseDepends on selected Martini deploymentYes for Edge Integration Cell: PostgreSQL or SAP HANA
Customer provides key-value datastoreDepends on architectureYes for Edge Integration Cell: Redis, Valkey, or SAP HANA
Customer provides load balancerDepends on architectureYes for Edge Integration Cell
Full design environment self-hostedRuntime development/deployment architecture controlled by customer according to planNo; Edge design and central management remain in SAP Integration Suite cloud
Data processed locallyYesYes with Edge Integration Cell
Hybrid central managementAvailable depending on deployment modelYes

SAP Edge Integration Cell has materially changed the deployment comparison. Integration scenarios can now be designed and monitored through SAP Integration Suite while executing within customer-managed private-cloud or on-premises Kubernetes infrastructure.

The production Edge Integration Cell architecture requires customer-operated Kubernetes plus persistent storage, an external database such as PostgreSQL or SAP HANA, a datastore such as Redis, Valkey, or SAP HANA, and a load balancer.

Edge Integration Cell remains connected to SAP Integration Suite and SAP BTP services for lifecycle and central management. It is therefore a hybrid runtime architecture rather than a completely independent installation of the entire SAP Integration Suite control plane.

Martini Customer Cloud similarly places integration processing inside customer infrastructure, but Martini is deployed as the application runtime itself rather than as an edge execution cell governed from a mandatory SAP cloud design plane.

Monitoring and Operations

CapabilityMartiniSAP Integration Suite
Message / execution historyTrackerMessage Processing Log
Search processed messagesYesYes
Status and durationYesYes
Error detailsYesYes
Step-level tracingYesYes
Configurable log levelsYesYes
Correlation identifiersYesYes
JMS queue monitoringYesYes
Automatic retry patternsYesYes
Manual retry of queued messagesYesYes for applicable queue scenarios
Download queued payloadTracker/payload accessYes for applicable JMS messages
Persistent transaction storeTrackerMessage queues, data stores, and processing logs depending on scenario
Generic stored transaction resubmissionYesRecovery depends on integration design and persistence mechanism
AI-assisted error resolutionAI troubleshooting capabilitiesYes

SAP Integration Suite's Message Processing Log provides structured information about integration-flow execution, including status, timestamps, processing duration, properties, logs, retry runs, and error information.

SAP also provides mature resilience patterns. Messages can be persisted to JMS queues or data stores so temporary failures can be retried automatically. Queue operators can inspect queued messages and manually retry applicable messages.

This differs from Martini Tracker's general transaction model. Martini can persist business transactions and payloads independently of whether the workflow was deliberately implemented around a retry queue, then search and resubmit selected transactions.

AI-Assisted Development and Agents

AI capabilityMartiniSAP Integration Suite
Generate integration flows from natural languageYesYes
Flow-step recommendationsYesYes
AI-assisted mappingYesYes through applicable mapping and Integration Advisor capabilities
Groovy script optimisationAI-assisted code developmentYes
AI-assisted error resolutionYesYes
API anomaly detectionMonitoring/AI integration capabilitiesYes
API traffic predictionAI-assisted operationsYes
Build runtime AI agentsYesSAP's wider BTP/Business AI platform provides agent capabilities; Integration Suite focuses on integration and tool exposure
MCP server artifactsYesYes
Deploy MCP server to managed runtimeYesYes, Integration Cell
Deploy MCP server to Edge Integration CellArchitecture supports customer-controlled MCP strategyNot currently supported according to current SAP deployment documentation
Expose APIs/integrations as AI toolsYesYes through MCP and API capabilities

SAP Integration Suite's AI features now include integration-flow generation from natural-language descriptions, next-step recommendations, Groovy script optimisation, AI-assisted error resolution, API anomaly detection, and API traffic prediction.

SAP also supports MCP Server artifacts within API Management. Current documentation states that MCP Server artifacts can be deployed to the SAP-managed Integration Cell runtime, while API artifacts can deploy to both Integration Cell and Edge Integration Cell.

SAP's AI proposition benefits from the wider SAP Business AI and BTP ecosystem, particularly where agents need governed access to SAP business processes and data.

Martini's approach is more workflow-native: agents, tools, APIs, services, events, database operations, and custom Java code are intended to share the same Martini orchestration runtime.

Event-Driven Architecture

CapabilityMartiniSAP Integration Suite
Publish/subscribe integrationYesYes
Kafka integrationYesYes
AMQPYesYes
JMSYesYes
Cloud message brokersAWS, Azure, Google and other broker integrationsSAP Event Mesh plus third-party adapters
Managed event brokerCan integrate external broker servicesYes, Event Mesh
Distributed event meshCan integrate distributed message infrastructureYes, Advanced Event Mesh
SAP-native business eventsConsumed through APIs/eventsMajor strength
Event visualization and managementExternal broker/monitoring toolingAdvanced Event Mesh provides dedicated event-management tooling

SAP Integration Suite provides both an Event Mesh capability for event-driven integration and the separately positioned Advanced Event Mesh for larger distributed event-driven architectures.

Advanced Event Mesh supports distributed event brokers across hybrid, multi-cloud, and edge environments and is especially valuable when organisations need event streaming closely integrated with SAP application events.

Martini integrates with message brokers and event systems but does not attempt to replace enterprise event-broker products. It treats brokers such as Kafka, ActiveMQ, RabbitMQ, Azure Service Bus, AWS messaging services, and other event infrastructure as endpoints within the integration architecture.

Martini vs SAP Integration Suite Pricing

Martini and SAP Integration Suite both publish meaningful list pricing, but they use different units.

Martini counts one distinct workflow or service execution as a transaction. SAP Integration Suite subscriptions include a monthly number of messages, and additional message capacity is sold in blocks.

SAP also applies message-size rules: a message up to 250 KB counts as one message, while additional 250 KB portions can increase the metered message count.

Martini pricing

FeatureEssentialsElasticCustomer Cloud
Starting price$495/month$3,995/month$4,500/month
Martini transactions100,000/monthUnlimitedUnlimited
API connector feesNoneNoneNone
Production1 production server3 load-balanced production serversConfigurable production servers
Included production capacityDefined production server12 vCPUs total12 vCPUs total
DeploymentLonti-managedIsolated Lonti-managed environmentCustomer cloud or on-premises

SAP Integration Suite pricing

FeatureStarterStandardEnhanced
Current published US monthly price$1,728$5,339$7,688
Included messages/month50,00010,000500,000
Tenants1+1+1+
Prebuilt contentIncludedIncludedIncluded
Custom Cloud IntegrationUp to 10 custom iFlowsIncludedIncluded
B2B libraries and Trading Partner ManagementNot includedIncludedIncluded
Open ConnectorsNot includedIncludedIncluded
API ManagementNot includedIncludedIncluded
Integration AdvisorNot includedIncludedIncluded
Edge Integration CellNot included1+1+
Alert Notification ServiceNot includedNot includedIncluded
Cloud Transport ManagementNot includedNot included in base editionIncluded
Advanced Event Mesh tenantNot includedNot included in base editionOne Advanced Event Mesh 100 tenant included

SAP's current US pricing page lists Starter at $1,728/month, Standard at $5,339/month, and Enhanced at $7,688/month.

The apparently lower included message allowance on Standard compared with Starter reflects the substantial additional platform capabilities included in Standard rather than a simple volume progression between tiers.

Additional SAP messages

Add-onCurrent published US price
10,000 additional transactions/messages per month$7/month
Additional Edge Integration Cell tenant$3,455/month

SAP's current pricing page also states that SAP-to-SAP application integrations using qualifying prebuilt content receive unlimited free messages.

Martini Transactions vs SAP Integration Suite Messages

How Martini counts a transaction

A Martini transaction is one distinct execution of a workflow or service.

  • Workflow steps
  • Transformations
  • Database operations
  • Internal service calls
  • External API calls
  • Message operations
  • Custom code executed inside the workflow

Those operations remain part of the same Martini transaction when they occur inside one workflow or service execution.

How SAP counts integration messages

SAP defines an integration message as an electronic communication processed through capabilities such as Cloud Integration, API Management, or Open Connectors.

Message size affects metering. Up to 250 KB is one message. Data above 250 KB is counted in additional 250 KB blocks or portions according to SAP's published usage terms.

SAP's service-description material also distinguishes other message categories. Edge messages and Event Mesh messages can use different conversion ratios when additional-message transactions are calculated.

SAP Cloud Integration flow execution is not simply one message

The number of SAP-metered messages can depend on how the integration flow exchanges data with receiver systems. Message size, multiple receivers, split processing, and synchronous request/response behaviour can affect message metering.

For that reason, a business process that appears conceptually equivalent to one Martini workflow execution should not automatically be assumed to equal exactly one SAP message.

DimensionMartiniSAP Integration Suite
Primary unitWorkflow/service executionMessage / transaction entitlement
Internal workflow stepsNot separately meteredNot normally priced simply as one charge per visual step
Payload sizeDoes not multiply transaction countCan multiply message count above 250 KB
Multiple receiver messagesRemain within workflow transactionCan affect SAP message metering
Splitter-generated outbound messagesDo not create additional Martini transactions by themselvesCan count as separate SAP messages
SAP-to-SAP prebuilt contentNormal Martini transaction modelQualifying messages are advertised as unlimited/free
High-volume fixed-price optionElastic and Customer CloudNo publicly advertised completely unlimited general-purpose message plan identified

Do Martini and SAP Integration Suite Offer Unlimited Usage?

Martini

Yes. Lonti Elastic, from $3,995/month, and Customer Cloud, from $4,500/month, include unlimited Martini transactions.

Unlimited transactions does not mean unlimited compute. Runtime throughput remains constrained by provisioned capacity.

SAP Integration Suite

SAP's current public plans provide defined monthly message allowances rather than a generally unlimited message entitlement.

Additional message capacity can be purchased in blocks of 10,000 transactions per month.

An important exception is SAP's current pricing statement that qualifying SAP-to-SAP application integrations using prebuilt content receive unlimited free messages.

This exception can make SAP's economics particularly attractive for organisations whose integration estate is dominated by qualifying standard SAP-to-SAP integrations.

Which Platform Fits Your Use Case?

SAP Integration Suite

SAP-centric enterprise landscape

Consider SAP Integration Suite when SAP S/4HANA, ECC, SuccessFactors, Ariba, SAP cloud applications, IDoc, RFC, OData, SAP events, and prebuilt SAP integration packages form a substantial part of the integration estate.

SAP Integration Suite

SAP-to-SAP standard integrations

Consider SAP Integration Suite when qualifying SAP-to-SAP requirements can use SAP's prebuilt content. SAP currently advertises unlimited free messages for these integrations.

SAP Integration Suite

B2B and trading-partner integration

Consider SAP Integration Suite when dedicated trading-partner management, EDI libraries, partner agreements, AS2, Integration Advisor, MIGs, and MAGs are major requirements.

SAP Integration Suite

Distributed event mesh

Consider SAP when the organisation wants event-broker infrastructure and event-stream governance as part of the same integration vendor portfolio through Event Mesh and Advanced Event Mesh.

SAP Integration Suite

SAP Process Orchestration migration

Consider SAP Integration Suite when modernising an existing SAP PI/PO estate. SAP provides Migration Assessment, migration tooling, runtime profiles, and Edge Integration Cell specifically relevant to this transition.

Martini

Developer-led Java backend integration

Consider Martini when integrations need direct access to arbitrary Java classes, JAR files, Spring libraries, Groovy services, and backend application logic rather than primarily script and adapter extensibility.

Martini

Native custom GraphQL API development

Consider Martini when teams need to build arbitrary GraphQL schemas, mutations, subscriptions, and resolvers. SAP API Composition provides valuable GraphQL access to business data graphs but solves a more specialised semantic-data problem.

SAP Integration Suite

API management

Consider SAP Integration Suite when a dedicated enterprise API lifecycle platform with Developer Hub, policies, products, subscriptions, semantic API Composition, and multiple managed or edge API runtimes is central to the programme.

Both

Git-first software engineering

Both now support serious Git-based workflows. SAP Cloud Integration integrates directly with GitHub branches, while Martini is designed around normal Git repositories independent of a specific hosting provider.

Both

Customer-controlled integration processing

Both can run integration workloads inside customer-controlled infrastructure. SAP uses Edge Integration Cell on Kubernetes while retaining central SAP cloud design and governance; Martini deploys the Martini Runtime itself.

Martini

Simpler private runtime architecture

Consider Martini when private deployment is required but the organisation does not want the Kubernetes, external database, key-value datastore, load-balancer, and cloud-lifecycle dependencies of an Edge Integration Cell architecture.

Martini

Predictable high-volume non-SAP integration

Consider Martini when high-volume integrations span arbitrary APIs and applications and a fixed-price unlimited-transaction model is preferable to message-volume entitlements.

SAP Integration Suite

AI-assisted SAP integration development

Consider SAP Integration Suite when AI-assisted iFlow generation, Groovy optimisation, Integration Advisor, API analytics, and the broader SAP Business AI ecosystem are important.

The Bottom Line

Martini and SAP Integration Suite overlap substantially across application integration, APIs, messaging, event-driven architecture, hybrid deployment, source control, monitoring, and AI-assisted development.

SAP Integration Suite's centre of gravity is enterprise integration across SAP and heterogeneous landscapes. Its strongest advantages include SAP-native connectivity, thousands of prebuilt integration assets, API Management, API Composition, B2B and Trading Partner Management, Integration Advisor, Event Mesh, Advanced Event Mesh, and SAP-specific migration tooling.

Martini's centre of gravity is developer-first low-code integration and backend development. It combines REST and GraphQL APIs, workflows, databases, messaging, events, Java extensibility, Git, CI/CD, monitoring, and deployable runtimes while allowing developers to work outside predefined connector and script abstractions.

The commercial models also differ. SAP subscriptions combine edition capabilities with monthly message entitlements and additional message blocks. Martini uses a workflow/service transaction model and then removes transaction metering on Elastic and Customer Cloud.

Do we primarily need SAP's broad enterprise integration ecosystem and deep SAP-specific capabilities, or a more developer-centric integration runtime that treats APIs, workflows, Java code, and backend services as one software project?

Evaluate Martini and SAP Integration Suite with the Same Project

Because SAP Integration Suite has substantial specialised capabilities, evaluate both products using an integration representative of your production estate rather than a simple prebuilt SAP demo.

  1. Consume a REST API.
  2. Consume a SOAP service.
  3. Consume a GraphQL API.
  4. Build and publish a REST API.
  5. Implement a custom GraphQL API requirement.
  6. Connect to SAP S/4HANA or SAP ECC.
  7. Connect to a relational database.
  8. Transform a complex nested payload.
  9. Consume or publish a Kafka or AMQP event.
  10. Use a packaged SAP integration or adapter.
  11. Implement a requirement not covered by the packaged adapter.
  12. Add custom Groovy logic.
  13. Reuse an existing enterprise Java or Spring library or implement the closest SAP equivalent.
  14. Create reusable integration subprocesses.
  15. Commit integration assets to GitHub.
  16. Develop changes on a branch and review them through a pull request.
  17. Promote the integration from development to test and production.
  18. Deploy integration processing inside customer-controlled infrastructure.
  19. Configure durable messaging and retry behaviour.
  20. Generate a processing failure and inspect the Message Processing Log or Tracker.
  21. Retry or replay the failed business message.
  22. Build or expose an MCP tool.
  23. Compare metered usage for a 100 KB payload and a 750 KB payload.
  24. Compare the economics of one million SAP-to-SAP prebuilt messages and one million custom third-party integration messages.

Compare development effort, SAP connector coverage, custom-code flexibility, API capabilities, Git workflow, environment promotion, deployment architecture, Kubernetes requirements, operational recovery, B2B capabilities, event architecture, AI capabilities, message consumption, and expected production cost.

Worked pricing scenarios

50,000 Small Custom Integration Messages per Month

A simple custom integration processes 50,000 messages per month, each 250 KB or less, and does not require Standard-only capabilities.

Martini

Calculation
50,000 workflow executions = 50,000 Martini transactions
Plan
Essentials
Price
$495/month

SAP Integration Suite

Calculation
50,000 messages are included in Starter
Plan
Starter
Illustrative total
$1,728/month
MetricMartiniSAP Integration Suite
Business events50,00050,000
Metered usage50,000 transactions50,000 messages
Illustrative planEssentialsStarter
Published monthly price$495$1,728

This compares only a relatively simple custom-integration requirement. It does not imply that the Starter edition is functionally equivalent to the full SAP Integration Suite Standard or Enhanced editions.

50,000 Messages Requiring API Management

A workload processes 50,000 messages and requires SAP API Management, so Standard rather than Starter is used.

Martini

Plan
Essentials
Price
$495/month

SAP Integration Suite

Plan
Standard
Illustrative total
$5,367/month
MetricMartiniSAP Integration Suite Standard
Business messages50,00050,000
Base subscription$495$5,339
Additional usage$0 within Essentials allowance$28
Illustrative total$495$5,367

The majority of the SAP cost in this example is the Standard platform subscription rather than message overage. Standard also includes substantial additional functionality such as API Management, B2B capabilities, Open Connectors, Integration Advisor, and Edge Integration Cell.

1 Million Custom Integration Messages on SAP Standard

A custom integration estate requires SAP Standard capabilities and processes one million messages of 250 KB or less each month.

Martini

Plan
Elastic
Price
$3,995/month

SAP Integration Suite

Plan
Standard
Illustrative total
$6,032/month
MetricMartini ElasticSAP Standard
Messages / workflow executions1,000,0001,000,000
Volume treatmentUnlimited Martini transactions10,000 included + 990,000 additional
Published illustrative monthly price$3,995$6,032

This simplified example assumes one SAP message per business event and payloads at or below 250 KB. Real SAP metering can differ according to integration-flow architecture.

1 Million Messages on SAP Enhanced

An organisation requires Enhanced capabilities and processes one million custom integration messages each month.

Martini

Plan
Elastic
Price
$3,995/month

SAP Integration Suite

Plan
Enhanced
Illustrative total
$8,038/month

Enhanced includes additional capabilities beyond Standard, including Cloud Transport Management entitlement, Alert Notification Service entitlement, Document AI allocation, and an Advanced Event Mesh tenant.

10 Million Custom Integration Messages per Month

A high-volume Enhanced deployment processes ten million messages of 250 KB or less per month.

Martini

Plan
Elastic
Price
$3,995/month

SAP Integration Suite

Plan
Enhanced
Illustrative total
$14,338/month
MetricMartiniSAP Integration Suite
Monthly executions/messages10,000,00010,000,000
Message-volume chargingNone on ElasticAdditional message blocks
Illustrative monthly price$3,995$14,338

This example is relevant only for custom/general integration traffic. Qualifying SAP-to-SAP prebuilt integrations are subject to SAP's separate free-message treatment.

1 Million SAP-to-SAP Messages Using Qualifying Prebuilt Content

A large workload uses qualifying SAP prebuilt integration content between SAP applications.

Martini

Calculation
1,000,000 workflow executions
Plan
Elastic
Price
$3,995/month

SAP Integration Suite

Calculation
SAP advertises unlimited free messages for qualifying SAP-to-SAP application integrations using prebuilt content
Price
Depends on required SAP edition

This is an important SAP advantage. A comparison based only on general additional-message pricing would materially misrepresent SAP economics for qualifying prebuilt SAP-to-SAP integration scenarios.

10,000 Business Messages with 750 KB Payloads

Each business exchange is 750 KB, illustrating SAP's size-based message metering.

Martini

Calculation
10,000 workflow executions = 10,000 Martini transactions
Plan
Essentials
Price
$495/month

SAP Integration Suite

Calculation
Under the simplified size assumption, a 750 KB message represents approximately three 250 KB message units
MetricMartiniSAP Integration Suite
Business exchanges10,00010,000
Payload per exchange750 KB750 KB
Illustrative usage units10,000 transactionsApproximately 30,000 SAP message units

Payload size is commercially relevant to SAP message metering but does not multiply Martini's transaction count.

Workflow Complexity Increases Without Increasing Business Volume

A process still handles 50,000 business events per month but expands from five internal operations to twenty-five.

Martini

Before
50,000 transactions
After
50,000 transactions

SAP Integration Suite

Before
Message count depends on the integration's external message exchanges
After
Adding internal routing, mapping, scripts, and processing steps does not automatically mean twenty-five billable messages

Unlike simple action-metered automation products, SAP does not charge once for every visual iFlow step. The architecture of external message exchange is more commercially important than the raw number of internal design steps.

Private On-Premises Integration Runtime

An organisation needs production integration processing to occur inside its own private infrastructure.

Martini

Plan
Customer Cloud
Price
$4,500/month

SAP Integration Suite

Plan
Standard or Enhanced with Edge Integration Cell
Base subscription
From $5,339/month for Standard
MetricMartini Customer CloudSAP Edge Integration Cell
Customer-hosted executionYesYes
Cloud design/control dependencyDepends on selected Lonti management architectureCentral SAP Integration Suite design and lifecycle remain cloud-managed
Kubernetes mandatoryNoYes
Customer database requiredDepends on deploymentYes for production Edge architecture
Published starting software subscription$4,500/monthStandard from $5,339/month

Both can meet strict private-processing requirements, but the operational footprint differs significantly. Edge Integration Cell is a Kubernetes-based hybrid runtime with multiple customer-provided backing services.

What these scenarios show

The scenarios should not be interpreted as claiming that Martini is always less expensive than SAP Integration Suite. SAP's economics can be particularly favourable where qualifying SAP-to-SAP prebuilt content is used, and SAP editions include specialised functionality that Martini does not attempt to duplicate.

Martini cost drivers

  • Workflow or service execution volume on Essentials.
  • Selected Martini plan.
  • Runtime infrastructure capacity.
  • Managed versus customer-controlled deployment.
  • Optional infrastructure services.

SAP Integration Suite cost drivers

  • Starter, Standard, or Enhanced edition.
  • Monthly message volume.
  • Message payload size.
  • External receiver/message architecture.
  • Eligibility for free SAP-to-SAP prebuilt messages.
  • Edge Integration Cell tenants.
  • Advanced Event Mesh requirements.
  • AI Units after applicable promotional terms.
  • Additional SAP BTP services.
  • Customer Kubernetes, database, datastore, and infrastructure for Edge deployment.
  • Negotiated BTP Enterprise Agreement, CPEA, or other commercial terms.

SAP Integration Suite has a sophisticated edition-and-message model that rewards use of SAP-standard integration content and bundles significant enterprise integration capabilities. Martini uses a simpler workload model: workflow or service executions count as transactions, connector choice does not alter licensing, and transaction metering disappears on Elastic and Customer Cloud.

Frequently asked questions

What is the main difference between Martini and SAP Integration Suite?

Both are enterprise integration platforms. SAP Integration Suite is particularly broad across SAP application connectivity, Cloud Integration, API Management, semantic API Composition, B2B, Event Mesh, Advanced Event Mesh, Open Connectors, migration tooling, and SAP-specific integration content. Martini is more explicitly developer-centric and combines APIs, workflows, databases, messaging, event processing, Java extensibility, Git, CI/CD, and deployable runtimes in a smaller unified platform.

How much does SAP Integration Suite cost?

SAP's current US pricing page lists Starter at $1,728/month, Standard at $5,339/month, and Enhanced at $7,688/month. Starter includes 50,000 messages, Standard 10,000, and Enhanced 500,000. Additional message capacity is currently listed at $7 per block of 10,000 transactions per month.

How much does Martini cost?

Lonti Essentials starts at $495/month and includes 100,000 Martini transactions. Elastic starts at $3,995/month and includes unlimited Martini transactions. Customer Cloud starts at $4,500/month and includes unlimited Martini transactions with deployment in customer-controlled cloud or on-premises infrastructure.

What counts as a Martini transaction?

A Martini transaction is one distinct workflow or service execution. Multiple workflow steps, transformations, database operations, API calls, integrations, messaging operations, and custom logic inside that execution do not each create another Martini transaction.

What counts as an SAP Integration Suite message?

SAP describes a message as an electronic communication processed through Integration Suite capabilities. Messages are generally measured in 250 KB units, so larger payloads can count as multiple messages. Exact metering can also depend on integration architecture and the capability processing the traffic.

Does SAP charge for every iFlow step?

No. SAP message pricing is not simply an action-per-step model. Internal mappings, routing, scripts, and other iFlow steps do not automatically each become separate billable messages. External message exchanges, payload size, receiver patterns, splits, and the specific capability used are more relevant to message metering.

Does Martini offer unlimited transactions?

Yes. Lonti Elastic and Customer Cloud include unlimited Martini transactions.

Does SAP Integration Suite offer unlimited messages?

SAP's general plans have defined monthly message allowances rather than an unlimited general-purpose message entitlement. However, SAP currently advertises unlimited free messages for qualifying SAP-to-SAP application integrations using prebuilt content.

How many prebuilt integrations does SAP Integration Suite provide?

SAP's current pricing page advertises more than 3,400 prebuilt integrations for SAP, third-party, and e-government applications.

Does Martini have connectors like SAP Integration Suite?

Yes, but SAP has a substantial packaged-connectivity advantage for SAP applications and a large catalogue of integration content. Martini provides packages and native endpoints but places greater emphasis on open connectivity through REST, GraphQL, SOAP, AsyncAPI, databases, files, webhooks, messaging, and custom Java code without connector-specific API licensing.

Can SAP Integration Suite run on premises?

Yes. Edge Integration Cell can execute supported integration flows and API workloads in customer-controlled private-cloud or on-premises Kubernetes infrastructure. Integration design, lifecycle management, and central governance remain connected to SAP Integration Suite in the cloud.

Can Martini run on premises?

Yes. The Martini Runtime can be deployed inside customer-controlled cloud or on-premises infrastructure through Customer Cloud.

What infrastructure does SAP Edge Integration Cell require?

SAP documents Kubernetes as the runtime platform. Production deployments also require persistent storage, an external PostgreSQL or SAP HANA database, a Redis, Valkey, or SAP HANA datastore, and a load balancer. Customers operate this infrastructure.

Does SAP Integration Suite support Git?

Yes. Current Cloud Integration Git Access supports configured GitHub repositories. Developers can import integration artifacts from repository branches and push or pull artifacts between Cloud Integration and selected branches.

Does SAP Integration Suite support GitLab or Bitbucket directly?

The current Cloud Integration Git Access documentation reviewed describes direct GitHub repository integration. A directly equivalent Cloud Integration GitLab or Bitbucket integration was not identified in that current documentation. External DevOps processes and SAP transport APIs provide other automation options.

Do both Martini and SAP Integration Suite support CI/CD?

Yes. Martini uses ordinary Git repositories and mainstream CI/CD systems directly. SAP combines GitHub integration, Integration Suite APIs, content transport, artifact versioning, and SAP Cloud Transport Management for controlled environment promotion.

Can SAP Integration Suite use custom code?

Yes. Cloud Integration supports Groovy and Java script steps, reusable Script Collections, custom adapters, mappings, and external services. SAP recommends staying within documented and supported runtime APIs and libraries to maintain upgrade compatibility.

Can Martini use custom Java libraries?

Yes. Martini can directly use Java classes, arbitrary JAR files, Spring libraries, Groovy methods, custom functions, and scripts inside normal Martini projects.

Can both platforms consume GraphQL APIs?

Yes, although the development experience differs. Martini has native GraphQL consumption tooling. SAP can integrate GraphQL services through HTTP and API integration patterns and exposes GraphQL itself through API Composition.

Can SAP Integration Suite expose GraphQL APIs?

Yes in a specific form. API Composition can expose a semantically connected business data graph through GraphQL as well as OData V4. This is different from Martini's general-purpose GraphQL API development model, where developers define arbitrary schemas, queries, mutations, subscriptions, and resolvers.

Does SAP Integration Suite provide API management?

Yes. API Management provides API design, security, traffic management, lifecycle governance, Developer Hub, subscriptions, products, policies, monitoring, and multiple runtime models including Integration Cell and Edge Integration Cell.

Does SAP Integration Suite support B2B and EDI?

Yes. Standard and Enhanced include B2B libraries and Trading Partner Management. Integration Advisor provides type systems, Message Implementation Guidelines and Mapping Guidelines for B2B, B2G, and A2A scenarios.

Does SAP Integration Suite support event-driven architecture?

Yes. SAP provides Event Mesh for publish/subscribe event integration and Advanced Event Mesh for larger distributed event-driven architectures spanning hybrid, multi-cloud, and edge environments.

Can SAP Integration Suite retry failed messages?

Yes. Cloud Integration supports several retry patterns, including JMS-backed persistence, data-store patterns, and adapter-specific retry mechanisms. Messages in applicable non-exclusive JMS queues can also be manually retried.

How does Martini Tracker differ from SAP Message Processing Log?

SAP Message Processing Log focuses on middleware message execution, status, trace information, retries, and integration-flow diagnostics. Martini Tracker is designed as a persistent business-transaction store that can retain transaction payloads and metadata and support direct search and resubmission across integrations.

Does SAP Integration Suite have AI-assisted development?

Yes. Current capabilities include AI-generated integration flows, flow-step recommendations, Groovy script optimization, AI-assisted error resolution, API anomaly detection, API traffic prediction, and AI-assisted B2B capabilities through Integration Advisor.

Does SAP Integration Suite support MCP?

Yes. SAP API Management supports MCP Server artifacts. Current documentation states that MCP Server artifacts can be deployed to the SAP-managed Integration Cell runtime. API artifacts can be deployed to both Integration Cell and Edge Integration Cell.

Is Martini an alternative to SAP Integration Suite?

Yes for many application integration, API, workflow, event, database, messaging, automation, and hybrid-runtime requirements. SAP Integration Suite has additional specialised strengths in SAP-native connectivity, SAP-to-SAP prebuilt content, B2B, semantic API Composition, Event Mesh, Advanced Event Mesh, and SAP migration tooling that should be considered separately.

Methodology

This comparison is based primarily on current first-party documentation and pricing information from Lonti and SAP.

  • Use current SAP Integration Suite pricing rather than historical CPI or legacy Integration Suite pricing.
  • Use the current Starter, Standard, and Enhanced public editions shown on SAP's pricing page.
  • Distinguish SAP subscription price from additional-message charges.
  • Use SAP's published 250 KB message-size rule when discussing message metering.
  • Do not automatically equate a business transaction or Martini workflow execution with one SAP Integration Suite message.
  • Recognise SAP's special treatment for qualifying SAP-to-SAP integrations using prebuilt content.
  • Distinguish Starter's ten-custom-iFlow limitation and reduced capability set from Standard and Enhanced.
  • Distinguish internal integration-flow steps from externally metered messages.
  • Represent SAP's July 2026 direct GitHub integration rather than relying on older descriptions of SAP Integration Suite lifecycle management.
  • Distinguish GitHub integration from SAP-specific artifact versioning and transport management.
  • Distinguish Edge Integration Cell from a completely disconnected self-hosted SAP Integration Suite deployment.
  • Include the infrastructure requirements of Edge Integration Cell when discussing customer-hosted deployment.
  • Distinguish SAP API Composition's GraphQL business-data graph from general-purpose custom GraphQL API development.
  • Distinguish Event Mesh from Advanced Event Mesh.
  • Acknowledge SAP's substantial strengths in SAP connectivity, B2B, EDI, trading-partner management, event architecture, API management, migration, and prebuilt content.
  • Treat AI functionality, MCP support, AI Units, plan inclusions, message entitlements, and pricing as time-sensitive.

The objective is not to claim that Martini is universally better than SAP Integration Suite. The objective is to show how a developer-centric integration and backend platform differs from SAP's broad enterprise integration platform across development model, connectivity, APIs, extensibility, deployment, DevOps, monitoring, events, B2B, AI, and commercial consumption.

Sources

Disclosure and Disclaimer

This comparison has been prepared by Lonti, the developer of Martini. It is intended to provide general information to organisations evaluating integration and automation platforms and should not be regarded as an independent or impartial product review.

Information about SAP Integration Suite is based primarily on publicly available information published by SAP, including SAP product pages, pricing pages, SAP Help Portal documentation, and SAP service-description material identified in the sources above. Information about Martini is based on Lonti's own product documentation and pricing.

We aim to keep this comparison accurate and current, but products, features, pricing, usage limits, message definitions, licensing terms, packaging, AI features, regional availability, and commercial arrangements may change without notice. Public documentation may also be incomplete or may not reflect individually negotiated SAP BTP Enterprise Agreements, CPEA arrangements, or other enterprise contracts. Readers should verify important information directly with the relevant vendor before making purchasing, architectural, or commercial decisions.

SAP Integration Suite message metering can depend on message size, integration architecture, selected capabilities, receiver patterns, splitting, Event Mesh processing, Edge Integration Cell processing, and other factors. Illustrative calculations on this page simplify these rules by explicitly stating their assumptions and should not be interpreted as SAP quotations or definitive billing calculations.

SAP currently advertises unlimited free messages for qualifying SAP-to-SAP application integrations that use prebuilt content. Worked examples involving custom or third-party integrations should not be applied to qualifying SAP-to-SAP scenarios.

SAP public pricing and plan entitlements vary by region and can change over time. Dollar figures shown on this page use SAP's publicly displayed US pricing at the date reviewed and exclude taxes, negotiated discounts, infrastructure, and related SAP BTP services unless explicitly stated.

Feature comparisons describe capabilities identified in publicly available documentation at the date shown on this page. The absence of a documented capability should not necessarily be interpreted as confirmation that the capability is unavailable.

Some AI and MCP capabilities can be subject to promotional, preview, AI Unit, regional, or edition-specific terms. Organisations should verify production availability and commercial terms directly with SAP.

This content is provided for general informational purposes only. Lonti makes no representation or warranty that the information is complete, error-free, or suitable for any particular organisation or use case. To the extent permitted by applicable law, Lonti accepts no liability for decisions or losses arising from reliance on this comparison. Nothing in this disclaimer excludes or limits any rights or remedies that cannot lawfully be excluded or limited.

All third-party product names, company names, logos, and trademarks are the property of their respective owners. Unless expressly stated otherwise, Lonti is not affiliated with, endorsed by, sponsored by, or associated with SAP.

Last reviewed: September 2026