# US 2026/0099465 A1 · Systems and methods for optimizing data for a serverless file system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099465 A1
- Document ID: US20260099465A1
- Status: Published application
- Kind: A1
- Application number: 19/418,030
- Filed: 2025-12-12
- Published: 2026-04-09
- Earliest claimed: 2023-09-22
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Nour Omar; Louis Buell; Donald Gennetten
- Web page: https://patentgrep.com/patent/US20260099465A1

## CPC

- G06F 16/172: Caching, prefetching or hoarding of files
- G06F 16/164: {File meta data generation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Disclosed embodiments may include a system for optimizing data for a serverless file system. The system may receive input data and determine whether the input data is appropriate for optimization. If so, the system may optimize the input data to reduce a size to create optimized data, group the optimized data, apply metadata, versioning, tags, enterprise governance and compliance requirements to the optimized data and store the optimized data in a data repository. In response to receiving an input to upload the optimized data to the serverless file system and determining, from the metadata, that the optimized data is not stored in the serverless file system, the system may upload the optimized data to the serverless file system via an application programming interface. The system may update metadata of the optimized data to indicate a new location at which the optimized data is stored on the serverless file system.

## Claims

### Claim 1

A system comprising:
one or more processors;
memory in communication with the one or more processors and storing instructions that are configured to cause the system to:
receive input data;
determine a maximum size threshold based on an upload size restriction of a serverless file system and an expected percentage in data reduction from optimizing data for upload to the serverless file system;
determine whether the input data is appropriate for optimization by comparing a size of the input data to the maximum size threshold;
responsive to determining that the input data is appropriate for optimization:
optimize the input data to reduce a size to create optimized data;
apply metadata to the optimized data;
store the optimized data and the metadata in a data repository;
responsive to receiving an input to upload the optimized data to the serverless file system:
upload, from the data repository to the serverless file system, the optimized data; and
update, in the data repository, the metadata associated with the optimized data that is stored in the data repository to indicate a location at which the optimized data is stored on the serverless file system.

### Claim 2 (depends on 1)

The system of claim 1, wherein determining whether the input data is appropriate for optimization comprises:
identifying whether one or more dependencies exist;
responsive to identifying that the one or more dependencies exist:
determining whether a sum of a total size of the one or more dependencies is greater than 50 megabytes and less than 250 megabytes; and
responsive to determining that the sum of the total size of the one or more dependencies is greater than 50 megabytes and less than 250 megabytes:
determining that the input data is appropriate for optimization.

### Claim 3 (depends on 1)

The system of claim 1, wherein optimizing the input data further comprises one or more of:
determining a programming language of the input data;
responsive to determining the programming language of the input data:
completing language-specific size optimizations of the input data;
stripping object symbols from .so files;
deleting test folders; and
compressing the input data.

### Claim 4 (depends on 1)

The system of claim 1, wherein the metadata is configured to accommodate an indication of locations the optimized data is stored in the serverless file system.

### Claim 5 (depends on 4)

The system of claim 4, wherein optimizing the input data is completed by a first machine learning model, wherein the first machine learning model is trained to complete language-specific optimization of the input data based on prior examples of the input data and the optimized data.

### Claim 6 (depends on 3)

The system of claim 3, wherein completing the language-specific size optimizations of the input data comprises deleting object files in python, minifying files in JavaScript, or combinations thereof.

### Claim 7 (depends on 1)

The system of claim 1, wherein the memory stores further instructions that are configured to cause the system to: group the optimized data by:
locating dependencies in the optimized data; and
grouping, using heuristics, the optimized data such that inputs and outputs of the dependencies are located in a proximity to one another.

### Claim 8 (depends on 7)

The system of claim 7, wherein the grouping of the optimized data is completed by a second machine learning model based on prior examples of the input data and the optimized data.

### Claim 9 (depends on 1)

The system of claim 1, wherein the data repository is configured to locally store optimized data in a condition to be uploaded to the serverless file system upon command.

### Claim 10

A system comprising:
one or more processors;
memory in communication with the one or more processors and storing instructions that are configured to cause the system to:
receive input data;
determine a maximum size threshold based on an upload size restriction of a serverless file system and an expected percentage in data reduction from optimizing data for upload to the serverless file system;
determine whether the input data is appropriate for optimization by comparing a size of the input data to the maximum size threshold;
responsive to determining that the input data is appropriate for optimization:
optimize the input data to reduce a size to create optimized data;
apply metadata to the optimized data;
store the optimized data and the metadata in a data repository;
generate, based on a search command received via a graphical interface (GUI), an interactive search list, wherein the interactive search list shows results including the optimized data; and
receive, via the GUI, a user input indicating an instruction to upload the optimized data to the serverless file system.

### Claim 11 (depends on 10)

The system of claim 10, wherein the metadata is configured to accommodate an indication of locations the optimized data is stored in the serverless file system.

### Claim 12 (depends on 10)

The system of claim 10, wherein the interactive search list further comprises filters used to sort results and access control limitations that require user authentication to view certain results.

### Claim 13 (depends on 10)

The system of claim 10, wherein the memory stores further instructions that are configured to cause the system to:
upload, via an application programming interface, to the serverless file system, the optimized data.

### Claim 14 (depends on 10)

The system of claim 10, wherein the memory stores further instructions that are configured to cause the system to:
determine, from the metadata, whether the optimized data is stored in the serverless file system;
responsive to determining that the optimized data is not stored in the serverless file system:
upload, via an application programming interface, to the serverless file system, the optimized data;
update the metadata of the optimized data to indicate a new location at which the optimized data is stored on the serverless file system; and
responsive to determining that the optimized data is stored in the serverless file system:
reference the optimized data in the serverless file system.

### Claim 15 (depends on 10)

The system of claim 10, wherein the data repository is configured to locally store optimized data in a condition to be uploaded to the serverless file system upon command.

### Claim 16

A system comprising:
one or more processors;
memory in communication with the one or more processors and storing instructions that are configured to cause the system to:
receive input data;
optimize the input data to reduce a size to create optimized data;
apply metadata to the optimized data;
store the optimized data and the metadata in a data repository, the data repository being configured to locally store optimized data in a condition to be uploaded to a serverless file system upon command; and
responsive to determining that the optimized data is not stored in the serverless file system:
upload, from the data repository to the serverless file system, the optimized data; and
update, in the data repository, metadata associated with the optimized data that is stored in the data repository to indicate a location at which the optimized data is stored on the serverless file system.

### Claim 17 (depends on 16)

The system of claim 16, wherein the data repository is configured to locally store optimized data in a condition to be uploaded to the serverless file system based on the optimized data having a file size less than an upload size restriction of the serverless file system.

### Claim 18 (depends on 16)

The system of claim 16, wherein the memory stores further instructions that are configured to cause the system to:
modify a graphical user interface (GUI) to indicate that the optimized data has been uploaded to the serverless file system and the location at which the optimized data is stored; and
transmit the GUI to a user device.

### Claim 19 (depends on 16)

The system of claim 16, wherein the memory stores further instructions that are configured to cause the system to:
responsive to determining that the optimized data is stored in the serverless file system:
reference the optimized data in the serverless file system;
modify a graphical user interface (GUI) to indicate that the optimized data was already uploaded to the serverless file system and was referenced instead of reuploaded; and
transmit the GUI to a user device.

### Claim 20 (depends on 16)

The system of claim 16, wherein the memory stores further instructions that are configured to cause the system to apply enterprise governance and compliance requirements to the optimized data, wherein applying the enterprise governance and the compliance requirements comprises verifying security requirements and license needs for the optimized data.
