Satellite/Geospatial Data Lake

Principal workflows

• Ingest: Imagery and associated metadata arrive from the sources your organization approves, are checked and cataloged, and land in the storage tier that matches how often they will be used.
• Find and process: Analysts search the catalog by area, time and sensor, and analytic jobs, including change-detection models your teams choose, run on compute placed next to the storage.
• Review detections: Model outputs are candidates, not conclusions. Each candidate change is queued for an analyst, who confirms or rejects it and records the reason.
• Operate: Moraph monitors the environment, plans capacity, applies patches and approved changes, and reports on service and security each month.

Who uses it

• Geospatial intelligence program offices and mission data owners
• Imagery and geospatial analysts who search and exploit the holdings
• Data engineers and data scientists who build ingest pipelines and analytic models
• Information system security managers and authorizing officials responsible for the environment
• Inspectors and auditors who review access and configuration

Reporting

• Service performance, incidents and changes each month
• Storage and compute capacity against forecast intake
• Ingest health and rejected deliveries by source
• Candidate detections confirmed and rejected by model version
• Access grants and recertification status by collection
• Configuration baseline and drift for continuous monitoring

Features

• Tiered storage: Hot, warm and archive tiers with rules for when data moves between them, so frequently used imagery stays close to analysts and older holdings cost less to keep.
• Managed ingest pipelines: Pipelines for each approved source, with checks on arrival and a record of every file received, rejected or reprocessed.
• Geospatial catalog: Search by footprint, time, sensor and other metadata, with results filtered by the searcher's access.
• Compute next to the data: A shared pool of CPU and GPU compute for processing and model jobs, with quotas by program so one workload does not starve another.
• Model hosting: Run the change-detection and object models your organization selects, with each run recorded against the model version and data used.
• Analyst review queue: Model outputs are queued for analysts to confirm or reject, so no candidate detection is treated as a finding until a person decides.
• Data lineage: Every derived product records the source imagery, processing steps and model version that produced it.
• Access by holding: Access is granted per collection or program and follows the handling markings your organization assigns, with each grant recorded.
• Capacity planning: Storage and compute use tracked against forecast intake, so expansion is planned with your program office rather than made in an emergency.
• Configuration baseline: The approved configuration is documented and checked for drift, and differences are reported to your ISSM.
• Retention rules: Retention and disposition rules set by the data owner are applied by tier and collection, with a record of what was removed and when.
• Control evidence: Control mappings and evidence prepared for your RMF package and continuous monitoring, kept current as the environment changes.

Integrations

• Collection and commercial imagery sources: Feeds from the government and licensed commercial sources your organization approves, by file transfer or provider API.
• Exploitation and GIS tools: Analysts reach holdings from the tools they already use through standard geospatial services and file access.
• Model development environment: Models your data scientists build or select are registered and run on the lake's compute.
• Cross-domain solution: Where data must move between security domains, it goes through the cross-domain solution your organization has approved, not through the lake.
• Identity provider: Users sign in through your organization's identity provider, including certificate-based sign-in where required.
• Security monitoring: Platform and access logs forwarded to your security operations tooling.
• Moraph Work API: Service tickets, change requests and service reports available to your service management tools.

Deployment

• On your premises: Built in your data center or enclave, including classified environments, and operated under your organization's authority by cleared Moraph staff where the contract provides for it.
• US government cloud region: Built in a US government cloud region your organization has approved, hosted only in the United States.
• Hybrid: A cloud or central archive combined with storage and compute closer to where data is collected, scoped in the proposal.

Security and privacy

• Single sign-on: Users sign in through your identity provider, so your authentication policies, including certificate-based sign-in, apply.
• Access by role and holding: What each person can see follows their role and their grants by program and collection; platform operators do not see mission content.
• Encryption and keys: Data is encrypted at rest and in transit, with keys Moraph staff cannot use without explicit, time-bound authorization from your organization.
• Complete audit trail: Every search, retrieval, grant, change and export is logged with the person and time, and cannot be edited.
• Cleared US staff: Federal and defense work is handled only by US citizens with active clearances, and the environment is hosted only in the United States.
• Tested releases: Security testing gates every change to Moraph's tooling, and a software bill of materials is kept for the components Moraph supplies.

Limitations

• Moraph is not the manufacturer of the storage and compute hardware or the cloud provider. Their own service commitments, roadmaps and outages apply, and hardware, software and cloud licences are subject to their terms.
• Moraph does not hold an accreditation or authorization for the environment. Your authorizing official decides whether it operates; Moraph maps controls and supplies evidence to support that decision.
• Work in classified environments happens under your organization's authority and only where the contract provides for it, by US citizens with the required clearances.
• Moraph does not collect or task imagery. Data comes from the government and licensed commercial sources your organization provides, under their terms.
• Model outputs are candidates for analysts to review, not findings. Choosing, validating and interpreting analytic models is your organization's responsibility.
• Ingest and processing throughput depend on network links, hardware, data formats and workloads; they are sized during design rather than guaranteed in advance.
• Moving data between security domains is not included; it uses the cross-domain solution your organization has approved.
• The lake does not replace analysts' exploitation and GIS tools; it provides the storage, catalog and compute those tools draw on.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/satellite-geospatial-data-lake. Purchasing routes and company information: www.moraph.com/how-to-buy.