Replace legacy document archives with a modern, multi-cloud content server. Full ArchiveLink compliance with built-in OCR, invoice field extraction, and full-text search — turn archived documents into structured SAP data automatically. Deploy anywhere. 10–100x more affordable than OpenText or Hyland.
ArchiveLink Compliant
Cloud Platforms
More Affordable
Deployment Options
A drop-in replacement for legacy content servers. Fully compliant, cloud-native, and dramatically cheaper.
Complete implementation of the SAP ArchiveLink HTTP interface. Store, retrieve, search, and manage documents — every operation SAP expects, fully supported.
Store documents on Google Cloud, AWS, Azure, or your own servers. Use your existing cloud infrastructure — no vendor lock-in.
Built-in OCR, full-text indexing, and invoice field extraction. Turn scanned documents into searchable, structured SAP data — automatically, using your cloud provider's AI services.
Certificate-based authentication and cryptographic signature verification. The same enterprise-grade security model SAP uses natively.
Manage multiple document repositories from a single server. Each repository can use a different cloud provider and serve a different SAP system.
Intuitive web-based management console. Configure repositories, manage certificates, and monitor your content server — all from the browser.
Run on-premises, in Docker, or on any major cloud platform. Pre-built deployment configurations for Cloud Run, Kubernetes, ECS, and Azure Container Apps.
BDS Content Server connects directly to your SAP systems via the standard ArchiveLink interface. No custom development, no middleware, no changes to SAP.
Point your SAP ArchiveLink configuration to BDS Content Server. It speaks the same protocol SAP expects — your Basis team configures it like any other content server.
Select where documents are stored: Google Cloud, AWS, Azure, or your own infrastructure. Each repository can use a different storage provider.
SAP users continue working as usual. Documents are automatically stored, retrieved, and managed in the cloud. Zero disruption, zero retraining.
Start free for 120 days. Self-hosted on your cloud. Non-production licenses included with every paid plan. No feature difference in plans.
Evaluate with no commitment
No credit card required
For small SAP landscapes
~$8,000/system
For growing enterprises
~$7,000/system
For large SAP estates
~$6,000/system
Document Processing Add-on — $500/month
Automatic OCR, full-text keyword indexing, and invoice field extraction for up to 20,000 pages/month. Scales automatically in $500 blocks. Available on all plans. Learn more →
See how BDS Content Server compares to legacy archiving solutions.
| Vendor | Product | Annual Cost |
|---|---|---|
| Business Development Services | BDS Content Server | $8,000 – $48,000 |
| SAP (native) | SAP Content Server | $10K – $50K+ infra |
| OpenText | Extended ECM / Archive Center | $50K – $300K+ license |
| Hyland | OnBase for SAP | $100K – $1M+ license |
| KGS Software | tia | €10K – €100K+ |
| PBS Software | PBS Archive | €20K – €150K+ |
7 deployment options — from a standalone Linux binary to fully managed serverless containers.
Standalone binary on Linux. Systemd service. Full control.
Docker Compose for dev, testing, or simple deployments.
Serverless, auto-scaling, managed HTTPS. Workload Identity.
GKE, EKS, AKS. High availability, horizontal scaling.
Managed containers, IAM roles, S3 integration.
Serverless containers, Managed Identity, Blob Storage.
GCE, EC2, Azure VM. Same binary, cloud IAM.
End-to-end archiving project delivery by experienced SAP Basis architects. Bundled with BDS Content Server for a complete solution — reduce your HANA footprint, maintain SOX compliance, and modernize your archive storage in one engagement. Contact us for quotation.
Database analysis, archiving object identification, dependency mapping, and data volume assessment across FI, CO, MM, SD, PP, and Basis modules.
ADK Customizing, Archive Information System setup, retention policies, Archive Routing rules, background job scheduling, and BDSCONT content repository integration.
Retention time strategy per jurisdiction, SOX compliance validation, authorization design (S_ARCHIVE), archive file integrity verification, and internal audit sign-off support.
Wave-based production rollout, post-archiving database optimization, monitoring setup, runbook creation, and knowledge transfer to your operations team.
Bundled with BDS Content Server — Every archiving consultancy engagement includes BDS Content Server as the archive file storage backend. Replace legacy content servers and execute your data archiving project in a single, cost-effective engagement. View pricing →
Full support for ACDOCA (Universal Journal), MATDOC, HANA data aging, Fiori archiving apps, and ILM-based retention management.
Typical database footprint reduction across archivable tables. Potential to downsize your HANA license tier and reduce infrastructure costs.
Structured 9-phase methodology from discovery through production hypercare. 135–185 person-days of expert effort, tailored to your landscape.
SAP ERP on Oracle or DB2 reaches end of maintenance in 2027. Every customer must move to S/4HANA or BW/4HANA — and both run exclusively on SAP HANA, an in-memory database where every gigabyte lives in RAM.
SAP ERP (ECC 6.0) mainstream maintenance ends in 2027. Extended maintenance is available at a premium, but migration to S/4HANA is inevitable. The clock is ticking.
Unlike Oracle or DB2 where data sits on disk, HANA keeps your entire database in RAM. A 10 TB Oracle database running on 1.5 TB of RAM migrated to HANA requires 4 TB of RAM even with compression, data aging or NSE — and cloud VMs with that much memory cost a fortune.
Companies routinely see 3–5x infrastructure cost increases when migrating large ERP databases to HANA. Even with HANA’s column-store compression, the RAM and VM costs far exceed what you paid for traditional disk-based databases.
The solution: Archive first, then migrate. By archiving historical data before your S/4HANA migration, you dramatically shrink the database that needs to run in HANA memory. A 4 TB Oracle ERP database with 7+ years of transactional history can often be reduced to 1.5–2 TB after archiving — cutting your HANA infrastructure costs by 50% or more, permanently.
Years of FI documents, material movements, IDocs, change logs, and spool data accumulated in your ERP. On Oracle, disk is cheap. On HANA, this becomes 4 TB of RAM.
Archive 50–70% of historical data to BDS Content Server. Data remains fully accessible via SAP’s Archive Information System. SOX-compliant. Cloud-native storage at a fraction of RAM cost.
Migrate a lean database to S/4HANA. Smaller HANA instance, smaller cloud VM, smaller license. Ongoing archiving keeps it lean. Savings compound year over year.
SAP HANA licenses are sized by memory. Reducing your database from 4 TB to 1.5 TB can mean a significantly smaller — and cheaper — HANA license tier.
High-memory cloud VMs are the most expensive instance types. A 4 TB HANA VM costs multiples of a 1.5 TB VM. Archiving pays for itself before migration day.
Less data means shorter migration windows, faster DMO/SUM runs, and reduced project risk. Your S/4HANA go-live gets simpler and cheaper.
Designed by engineers who understand SAP ArchiveLink inside and out.
“We replaced a six-figure OpenText installation with BDS Content Server running on Cloud Run. Setup took a day. Our SAP team didn't notice any difference — except the invoices stopped coming from OpenText.”
SAP ERP end of maintenance is 2027. Shrink your database now, save on HANA infrastructure forever. Start with a free dev license or talk to our archiving team.