MAJESCO / SAPIENS CLOUD ARCHIVE

    Majesco / Sapiens Cloud Archive — Parquet on S3/Azure/GCS, Queryable, Tiered

    Majesco / sapiens cloud archive: turnkey product wrapping AWS S3 / Azure Blob / GCS with partition design, retention engine, RBAC and query UI for Majesco and Sapiens P&C and L&A data. Tiered warm/cold/archive storage. Customer-owned bucket and keys. <$5K/year typical storage cost.

    3 clouds
    AWS + Azure + GCS
    3 tiers
    Warm / cold / archive
    $<5K/yr
    Typical storage cost
    Customer-owned
    Bucket + KMS keys

    What majesco / sapiens cloud archive actually is — and why it isn't just a Data Lake export

    Majesco Data Lake and Sapiens IDIT data services dump Parquet to a bucket. That is raw material, not an archive product. Majesco / sapiens cloud archive adds everything you need to make that material safe, queryable and audit-ready for 30+ years.

    P&C and L&A insurers have spent the last decade extracting policy and claim data into 'data lakes' — buckets full of CSV, Avro and Parquet files dumped from Majesco P&C Core Suite, Sapiens IDITSuite or legacy on-prem databases. Without a production layer on top, those buckets are operationally useless for compliance: there is no per-jurisdiction retention enforcement, no immutable audit log of who accessed what, no RBAC for HIPAA / GDPR / SIU / legal-hold data classes, no exam-response packs ready for state-commissioner delivery, no attachment streaming for multi-TB claim documents and no self-serve query UI for business users.

    Majesco / sapiens cloud archive is the productised layer. Hash-signed Parquet partitioned by state / LOB / fiscal year sits in customer-owned S3, Azure Blob or GCS bucket, under customer-managed encryption keys. Tiered storage (warm/cold/archive) tracks query access pattern — recent data on Standard-IA for sub-second queries, mid-tier data on Glacier for minutes-latency, deep archive on Glacier Deep Archive for state-commissioner long-tail exams. Per-jurisdiction retention engine enforces 50-state + NAIC + NAIC #797 + HIPAA + reinsurance + SOX rules per record. RBAC, audit log and query UI ship pre-built.

    The output is an archive that costs less than $5K/year for typical mid-sized P&C/L&A carriers (5 TB structured + 30 TB attachments) while satisfying every overlapping retention and audit obligation. Same archive supports actuarial loss-triangle pivots, L&A mortality experience studies, claims-adjuster lookups, finance restatements, SIU fraud analytics, state-commissioner exam responses and reinsurance bordereaux audits — all from one Parquet layer queried through one UI.

    Cloud archive — three deployment dimensions

    1
    Cloud provider
    AWS S3 + Athena, Azure Blob + Synapse Serverless, GCS + BigQuery. Customer chooses based on enterprise standard. Multi-cloud supported for global data-residency.
    2
    Storage tier
    Warm (Standard-IA / Cool / Nearline) for 3-5yr recent. Cold (Glacier Flexible / Archive / Coldline) for 5-15yr mid-tier. Archive (Glacier Deep Archive) for 15+yr long-tail.
    3
    Encryption & keys
    Customer-managed KMS / Key Vault / Cloud KMS keys. Customer-owned bucket. VPC endpoints / Private Link for network isolation. Syntra never holds keys.
    4
    Retention engine
    50-state + NAIC + NAIC #797 + HIPAA + reinsurance + SOX + GDPR rules per record. Per-jurisdiction clocks. Tier transitions tied to retention status.

    The majesco / sapiens cloud archive product — six core capabilities

    What the platform ships pre-built on top of customer-owned cloud object storage.

    ☁️

    Multi-cloud storage

    AWS S3 (Standard-IA / Glacier / Deep Archive), Azure Blob (Hot / Cool / Archive), Google Cloud Storage (Standard / Nearline / Coldline / Archive). Customer-owned bucket. Customer-managed encryption keys.

    🌡️

    Tiered storage engine

    Warm tier for 3-5yr recent data with sub-second queries. Cold tier for 5-15yr with bulk pulls. Archive tier for 15+yr long-tail with 12-48hr retrieval. Auto-tier transitions tied to retention status.

    ⚖️

    Per-jurisdiction retention

    50-state + NAIC + NAIC #797 (L&A) + HIPAA + GDPR + reinsurance + SOX rules per record. Clocks run independently. Records can't be deleted until every applicable clock has expired.

    🔎

    Self-serve query UI

    Business users (actuarial, claims, finance, underwriting, SIU, compliance) query the archive without SQL or IT. Sub-second response on Parquet-partitioned data.

    🔐

    RBAC + audit log

    HIPAA / GDPR / SIU / legal-hold data classes gated by role at query level. Every query logged immutably with user identity, timestamp, returned record count and data classification.

    📦

    Exam-response packs

    Random-sample policy/claim retrieval for state-commissioner data calls, packaged with structured data + attachments + audit log as signed evidence bundles ready for examiner delivery.

    The majesco / sapiens cloud archive build — six stages

    From cloud bucket provisioning to live self-serve queries. Typical timeline: 8-12 weeks for the initial bulk archive plus ongoing incremental.

    1

    Cloud bucket & keys — Week 1

    Customer provisions cloud bucket (S3 / Azure Blob / GCS) in chosen region(s), creates customer-managed encryption key, defines IAM/RBAC policies. Syntra ETL platform configured with read-only access for ingestion writes and customer-controlled deletion rules.

    2

    Partition design — Week 1-2

    Partition scheme tuned to Majesco/Sapiens insurance retention patterns: state (admission + loss), LOB (P&C lines + L&A products), fiscal year. Sub-partitioning for high-volume LOBs (e.g., personal auto by accident year).

    3

    Tier strategy & retention rules — Week 2-3

    Warm/cold/archive tier policy tuned to insurance access patterns. 50-state retention rules + NAIC MAR + NAIC #797 + HIPAA + reinsurance + SOX + GDPR rules per record class. Tier transitions tied to retention status.

    4

    Bulk archive extract — Week 3-10

    Initial bulk extract of full Majesco/Sapiens history via Data Lake, IDIT data services, REST APIs and (for on-prem) JDBC. Hash-signed Parquet staged with per-state retention metadata. Multi-TB attachments streamed in parallel.

    5

    Query layer activation — Week 9-11

    Athena / Synapse / BigQuery query layer activated. Self-serve UI deployed for business users. RBAC + audit log enabled. Exam-response pack templates loaded.

    6

    Incremental + monitoring — Week 11 onward

    Scheduled incremental archive of newly-closed policies and newly-closed claims. Monthly storage-cost dashboards. Quarterly retention audit. State-commissioner exam response readiness reviews.

    Cost economics — what majesco / sapiens cloud archive replaces

    Convert per-policy live core system economics into <$5K/year cloud storage. Math is reproducible per customer.

    💸

    Live core licence

    Majesco Cloud Platform or Sapiens IDITSuite SaaS per-policy / per-user / per-transaction economics for 20+ years of closed policies and claims — typically 100-1000x more expensive than cloud archive storage.

    🖥️

    On-prem infrastructure

    Database licences (Oracle DB EE, SQL Server EE), application servers, OS-level support, DR backup infrastructure for legacy Majesco/Sapiens on-prem — typically $200K-$1M/year per instance.

    📦

    Tape & DR backup

    Tape backup regime for legacy DB backups, off-site rotation, tape library management, retrieval testing — typically $50K-$200K/year plus retrieval lag of weeks.

    🔧

    Operational staffing

    DBAs, sysadmins and Majesco/Sapiens-versioned developer knowledge required to keep legacy systems running — typically $200K-$800K/year per instance.

    ⚠️

    Compliance risk

    State-commissioner exam findings on unpatched legacy, HIPAA risk on legacy holding medical records, GDPR risk on legacy holding EU policyholder data — hidden but real cost.

    📈

    Performance drag

    Cold data in live core systems slows nightly batch, integration extracts, reporting and backups. Hidden opportunity cost across actuarial, claims, underwriting and finance teams.

    Frequently asked questions

    What is majesco / sapiens cloud archive?+

    Majesco / sapiens cloud archive is the productised archive layer for Majesco P&C/L&A Core Suite and Sapiens IDITSuite/CoreSuite/ALIS data: full Policy, Billing, Claims, Underwriting and Reinsurance history stored as hash-signed Parquet on customer-controlled cloud object storage (S3, Azure Blob, GCS), with tiered storage (warm/cold/archive), per-jurisdiction retention enforcement, RBAC for HIPAA/GDPR/SIU/legal-hold and self-serve query access. Unlike a raw bucket of CSV exports, majesco / sapiens cloud archive ships as a turnkey product: ingestion pipelines, partition design, retention engine, attachment streaming, audit logging, exam-response packs and query UI are all built in. Customers own the bucket and the encryption keys; the product runs on top.

    Why use cloud object storage for majesco / sapiens cloud archive?+

    Three reasons. Cost: S3 Standard-IA runs ~$12.50/TB/month, S3 Glacier ~$4/TB/month, Glacier Deep Archive ~$1/TB/month. Compare to per-policy Majesco Cloud Platform or Sapiens IDITSuite SaaS pricing for 20+ years of closed policies and claims — typically 100-1000x more expensive than cloud object storage. Durability: cloud object storage delivers 11-nines durability with cross-region replication options, far exceeding what an on-prem Majesco DB backup tape regime can provide. Queryability: modern columnar engines (Athena, Synapse Serverless, BigQuery, Trino) query Parquet directly with no data load required — meaning the archive is queryable without standing up a database server.

    How does majesco / sapiens cloud archive use tiered storage?+

    Three tiers tuned to query access pattern. Warm tier (S3 Standard-IA, Azure Cool, GCS Nearline) — recent 3-5 years of policy and claim data, queried frequently for active claims research, renewal underwriting, financial reporting; sub-second query latency. Cold tier (S3 Glacier Flexible Retrieval, Azure Archive, GCS Coldline) — 5-15 years, queried for actuarial loss-triangle pivots, reinsurance bordereaux audits; minutes-to-hours retrieval latency with bulk pulls. Archive tier (S3 Glacier Deep Archive) — 15+ years, queried for state-commissioner long-tail exams, asbestos/environmental liability discovery, historical L&A claims; 12-48 hour retrieval latency. Storage cost drops ~10x at each tier; per-jurisdiction retention rules govern when data flows between tiers.

    Does majesco / sapiens cloud archive support all three major clouds?+

    Yes. AWS S3 (Standard, Standard-IA, Glacier Flexible Retrieval, Glacier Deep Archive) with Athena query. Azure Blob (Hot, Cool, Archive) with Synapse Serverless query. Google Cloud Storage (Standard, Nearline, Coldline, Archive) with BigQuery query. Customers commonly choose to keep archive in the same cloud as their other enterprise data — e.g., AWS if they run Fusion on OCI but use AWS for analytics, Azure if Microsoft is the enterprise standard, GCS if BigQuery is the analytical platform. The same archive UI and query engine works across all three. Multi-cloud setups (e.g., one region per geography) are supported for global insurers with multi-jurisdiction data residency requirements.

    How is majesco / sapiens cloud archive different from a Majesco/Sapiens data warehouse export?+

    Majesco Data Lake and Sapiens IDIT data services emit Parquet to a bucket — useful raw material, but not an archive product. Majesco / sapiens cloud archive adds the production layer on top: partition design tuned to insurance retention patterns (state / LOB / fiscal year), retention engine that enforces 50-state + NAIC + NAIC #797 + HIPAA + reinsurance + SOX rules per record, attachment streaming for multi-TB unstructured data, RBAC at query level, immutable audit logging, exam-response packs ready for state-commissioner delivery and query UI for self-serve business access. A raw data warehouse export is the start of the journey; cloud archive is the finished product.

    Who owns the data and encryption keys in majesco / sapiens cloud archive?+

    The customer. The cloud bucket is provisioned in the customer's own AWS / Azure / GCP account, under their organisational policies and IAM controls. Encryption uses customer-managed keys (KMS, Key Vault, Cloud KMS) — Syntra ETL never sees or holds the keys. Customer-managed VPC endpoints / Private Link can isolate the archive from public internet entirely. Data egress, replication, retention policies and access logging all run under customer control. Syntra ETL provides the software, schemas, retention engine and query layer — but the data is in the customer's bucket, under the customer's keys, throughout.

    How does majesco / sapiens cloud archive handle global data-residency requirements?+

    Critical for global P&C and L&A insurers operating across US, EU/UK, APAC and Latin America. Each jurisdiction has data residency rules: GDPR for EU policyholder data, UK DPA for British data, LGPD for Brazilian data, APRA for Australian, MAS for Singapore. The cloud archive supports region-locked partitioning — EU policyholder data stays in EU buckets (eu-west-1, westeurope, europe-west2 etc.), US data in US buckets, APAC data in APAC buckets. Cross-region queries respect jurisdiction policies. RBAC additionally enforces data-subject-rights handling per jurisdiction — GDPR DSARs, CCPA opt-outs and equivalent.

    What does majesco / sapiens cloud archive cost?+

    Annual cost is dominated by cloud storage spend, which is small. A typical mid-sized P&C/L&A carrier with 5 TB structured + 30 TB attachments split across warm/cold/archive tiers spends $1-3K/year on AWS S3 (or equivalent on Azure/GCS) for storage plus a few hundred dollars on query-time charges for typical analytical workloads. Add the Syntra ETL platform subscription that runs the ingestion pipelines, retention engine, RBAC, audit log and query UI. Total annual spend is typically <$5K storage + platform subscription — versus six- or seven-figure annual cost of keeping the same data inside live Majesco or Sapiens infrastructure.

    Ready to price your majesco / sapiens cloud archive?

    Book a 30-minute working session. We'll inventory your Majesco or Sapiens data volumes, pick the right cloud (AWS/Azure/GCS) and tier strategy (warm/cold/archive), model your storage economics across 30 years of retention, and quote a customer-owned cloud archive that typically costs <$5K/year.