Now accepting pilot requests.
FileRelay
SAP document routing · ArchiveLink · CMIS · OData

One platform for SAP document routing — every edition, every destination.

ECC and S/4HANA on-premise via ArchiveLink. S/4HANA Cloud (Public + RISE) via CMIS or released OData. One routing layer, no SAP customization, deliver to SharePoint, S3, APIs, and 15+ destinations.

Self-hosted / on-prem
Customer-managed VPC
No SAP modification
ArchiveLink · CMIS · OData
Audit logs & retries
Per-customer encryption

Deploys inside your perimeter

Self-hosted, managed on-prem, or hosted on a dedicated single-tenant environment we build just for you. Same product, three operating models.

Self-hosted

Most control

You run it. Helm chart or Docker Compose, your cluster, your ops team. Documents never leave your network.

  • OpenShift, EKS, AKS, GKE, bare metal
  • Air-gapped deployments supported
  • Customer-managed secrets (Vault, KMS)
  • Full source access on enterprise tier
Time to deploy1–2 weeks

Managed on-prem

Your infra · we operate

We deploy and operate FileRelay inside your cloud account. You keep data residency; we handle ops.

  • Customer-owned VPC / subscription
  • 24/7 monitoring + SLA
  • Zero-touch upgrades
  • Dedicated tenant — no shared infra
Time to deploy2–5 days

FileRelay-hosted

Dedicated · we operate

We host and operate FileRelay on dedicated infrastructure built just for you. Same isolation as on-prem.

  • Dedicated single-tenant infra
  • Same product as self-hosted
  • We run deployment, ops & upgrades
  • No infra/ops team needed
Time to deploy1–3 days
See full deployment options
See FileRelay in action

Four walkthroughs: setup, audits, enrichment, S/4HANA

Setup with ArchiveLink

How FileRelay Works

Inside your FileRelay deployment, create a workspace and a repository. The ingest endpoints SAP will call are derived from their slugs.

Step 1
Workspace setup
Workspace
›acme-prod
Repository
›fi-invoices
Endpoints provisioned Active
Hosthttps://filerelay.your-domain.internal
ArchiveLink/acme-prod/fi-invoices/ContentServer
CMIS/acme-prod/fi-invoices/events/cmis
OData/acme-prod/fi-invoices/events/odata

On your FileRelay instance, create a workspace per environment (dev / prod) and a repository per SAP system. FileRelay generates the ArchiveLink Content Server URL automatically — the same repository also accepts CMIS webhooks and OData events at sibling paths.

Workspace Setup
Connect SAP
Connect Destination
Documents Flow
Protocol comparison

Not sure which one applies to your SAP?

FileRelay supports three SAP ingest protocols, matched to your edition. Take a quick look — then use the picker to confirm.

ArchiveLink
ECC · S/4 on-prem · RISE

SAP pushes documents to FileRelay in real time. Configured via classic SAPGUI (OAC0). No ABAP needed.

CMIS
S/4 Cloud Public & RISE

FileRelay polls the SAP Document Management Service via the OASIS CMIS 1.1 standard. Configured in Fiori.

OData
S/4 Cloud Public & RISE

FileRelay consumes released attachment OData APIs. Best when documents are tied to specific business objects.

Read the full comparison

Security and Compliance

Encryption per customer, audit on everything, on-prem by default.

Data residency

Documents stay in your network — your cluster or your cloud.

Per-customer encryption

Envelope encryption with KMS-backed keys, scoped per customer.

Audit trail

Every action logged with actor and outcome. Exportable for reviews.

Compliance roadmap

GDPR today. SOC 2 Type I in 2026 Q4. Honest about what’s live vs planned.

Certifications & standards

Ready
GDPR
Planned
SOC 2 Type I
Planned
SOC 2 Type II
Planned
ISO 27001
Planned
ISAE 3402
Planned
TISAX
Planned
HIPAA
Full security model

Supported Destinations

Route SAP documents to any of these systems.

Cloud Storage
4 available
Object Storage
4 available
Enterprise DMS
2 available
Custom / API
5 available

Need a destination we haven't built yet?

OpenText, Documentum, and other enterprise systems are on the roadmap. Tell us which you need and we'll prioritize it for your launch.

Everything you need to route SAP documents

A complete platform for SAP document routing with powerful automation.

Dashboard
Docs
Sync
API
Err

Real-Time Dashboard

Track documents, monitor storage, and view daily throughput from a single pane of glass.

Z1
Z2
GD
SP

Pipeline Routing

Map each SAP repo to a cloud folder. Documents route automatically on arrival.

rfc-console
> BAPI_DOCUMENT_GETLIST
OBJECTTYPE = "BKPF"
Result: 247 entries
Status: SUCCESS

RFC Console

Run SAP function modules (BAPI/RFC) from the browser via SAP’s Java Connector (JCo).

Certificate Management

SAP sends certs automatically. Activate, deactivate, monitor from one place.

Webhooks & Events

Get notified on every document event. Trigger downstream workflows.

doc-4821 → S3
doc-4822 → S3 (retry 1)
doc-4822 → S3
doc-4823 → dead letter
Email alert sent
Export

Retry & Recovery

Automatic retries with backoff. Supports failure email alerts and exportable reports.

GET/api/documents
POST/api/jco/call
GET/api/certificates
POST/api/connectors
{ "success": true }

Developer API

Full REST API with key auth. Access documents and connectors programmatically.

Production
QA
Development

Workspaces

Isolate multiple SAP systems in separate workspaces.

14:23Doc received
14:23Enriched via RFC
14:23Forwarded → Drive
14:22Cert verified
14:22Doc received

Audit Trail

Full history of every document. Compliance-ready with CSV export.

Why buy FileRelay instead of building it?

You could ship an SAP document routing layer on BTP, ABAP, CAP, or your own stack — implementing ArchiveLink, CMIS, or OData yourself. People do. Here’s what they discover in month 6.

Time
< 1 day vs 8–12 weeks

First document routed afternoon-of, not next quarter.

Destinations
15+ on day one

Add a new destination in minutes, not weeks. OAuth and API drift handled.

Certification
SAP ICC BC-HCS 4.5

We’re pursuing it. If you build, you spend 12–18 months and 5–6 figures.

Operations
Retries, audit, replay

The boring production-grade stuff that decides whether a build makes it past pilot.

See the full comparison

Frequently Asked Questions

Everything you need to know about routing documents out of SAP — ArchiveLink, CMIS, or OData.

Trust, Security & Compliance

How it works / Technical

Developer API

Build on top of FileRelay

API Reference
GET/api/documents
GET/api/documents/:id
GET/api/documents/:id/content
POST/api/documents/:id/forward
GET/api/repositories
GET/api/certificates
POST/api/jco/call
GET/api/stats
# Example: fetch all documents
curl -H "Authorization: Bearer sk_..." \
https://yourco.filerelay.io/api/documents

Full REST API with API key authentication. Access your documents, metadata, repositories, and connectors programmatically. Build custom integrations, automate workflows, or embed FileRelay into your existing systems.

REST API
Full CRUD for documents, repos, certs, and connectors
API Keys
Generate keys, set permissions, track usage
Webhooks
Get notified on document arrival, forwarding, and errors
SAP RFC Bridge
Call SAP function modules (BAPI/RFC) over HTTP via SAP’s Java Connector (JCo)
View API Documentation

One account. Multiple SAP systems.

Each workspace is fully isolated — its own endpoint, documents, connectors, and certificates.

Production45,230 docs
QA12,847 docs
Development3,102 docs