DCT
8:25-cv-01889
Smartsuite Holdings Inc v. Codeblox LLC
Key Events
Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: SmartSuite Holdings, Inc. (Delaware)
- Defendant: CodeBlox, LLC (Florida)
- Plaintiff's Counsel: King & Spalding LLP
- Case Identification: 8:25-cv-01889, C.D. Cal., 08/25/2025
- Venue Allegations: Plaintiff SmartSuite alleges venue is proper in the Central District of California because Defendant CodeBlox is subject to personal jurisdiction in the district, stemming from demand letters sent into the district, and is therefore deemed to reside there for venue purposes.
- Core Dispute: Plaintiff seeks a declaratory judgment that its work management software platform does not infringe two patents owned by Defendant related to graphical user interface-based application development environments.
- Technical Context: The technology pertains to low-code/no-code development platforms, which enable users with little to no programming expertise to build software applications through visual interfaces.
- Key Procedural History: The action was precipitated by demand letters sent by CodeBlox to SmartSuite on January 30, 2025, and June 20, 2025, which alleged infringement and threatened litigation. After SmartSuite provided non-infringement arguments that were not accepted by CodeBlox, SmartSuite filed this declaratory judgment action to resolve the controversy.
Case Timeline
| Date | Event |
|---|---|
| 2010-01-01 | Archer Technologies purchased by EMC Corporation |
| 2018-05-09 | Priority Date for '889 and '370 Patents |
| 2021-01-01 | SmartSuite founded |
| 2022-03-08 | U.S. Patent No. 11,269,889 Issues |
| 2023-11-28 | U.S. Patent No. 11,829,370 Issues |
| 2025-01-30 | CodeBlox sends first demand letter to SmartSuite |
| 2025-06-20 | CodeBlox sends second demand letter with draft complaint |
| 2025-08-07 | SmartSuite counsel informs CodeBlox of review |
| 2025-08-19 | CodeBlox sends email indicating intent to file suit |
| 2025-08-22 | SmartSuite sends non-infringement letter to CodeBlox |
| 2025-08-25 | Complaint for Declaratory Judgment filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 11,829,370 - "GRAPHICAL USER INTERFACE DRIVEN PROGRAMMING DEVELOPMENT ENVIRONMENT"
- Patent Identification: U.S. Patent No. 11,829,370, "GRAPHICAL USER INTERFACE DRIVEN PROGRAMMING DEVELOPMENT ENVIRONMENT," issued November 28, 2023.
The Invention Explained
- Problem Addressed: The patent's background section describes the high barrier to software development, noting that it typically requires extensive expertise in programming languages, data structures, and algorithms, which many individuals and businesses lack '370 Patent, col. 1:21-34
- The Patented Solution: The invention is a system that allows non-expert users to create applications using intuitive visual tools like point-and-click interfaces '370 Patent, col. 4:13-20 User designs are captured as "metadata" (e.g., JSON files) and stored in a database '370 Patent, abstract At runtime, a web service interprets this metadata to dynamically generate and execute underlying software code (e.g., C#, SQL), bypassing traditional compilation and deployment cycles '370 Patent, col. 4:20-24 This architecture is depicted as comprising separate databases for metadata and user data '370 Patent, Fig. 1
- Technical Importance: This metadata-driven approach enables rapid development and modification of applications by users without formal programming skills, allowing businesses to more quickly adapt software to their specific needs '370 Patent, col. 5:1-10
Key Claims at a Glance
- The complaint seeks a declaration of non-infringement with respect to the claims of the '370 Patent, focusing on independent claim 1 Compl. ¶25
- The essential elements of independent claim 1 include:
- A system comprising a processor and memory.
- "a metadata database" for storing application data elements and metadata structures.
- "a user database" for storing user data comprising user-defined values.
- A web service that performs operations including:
- Receiving an updated value for a data element.
- Retrieving and parsing the corresponding application data element from the metadata database.
- Updating a value of a data field.
- Storing the updated data element in "either the metadata database or the user database."
- Automatically generating an update statement.
- Allowing for execution of software code "without using any software deployment processing" like compilation or linking Compl. ¶25
U.S. Patent No. 11,269,889 - "GRAPHICAL USER INTERFACE DRIVEN PROGRAMMING DEVELOPMENT ENVIRONMENT"
- Patent Identification: U.S. Patent No. 11,269,889, "GRAPHICAL USER INTERFACE DRIVEN PROGRAMMING DEVELOPMENT ENVIRONMENT," issued March 8, 2022.
The Invention Explained
- Problem Addressed: The patent addresses the technical expertise required for conventional software application development, which poses a significant hurdle for businesses and non-programmers '889 Patent, col. 1:21-34
- The Patented Solution: The patented system provides a graphical environment where users can visually define data structures and application logic '889 Patent, abstract These definitions are stored as metadata, which is then used at runtime to dynamically generate and execute software code, such as C# and SQL, to implement the application's functionality '889 Patent, col. 4:13-24 The architecture, illustrated in Figure 1, includes distinct storage for "Meta Data" and "User Data" '889 Patent, Fig. 1
- Technical Importance: The invention aims to democratize software development by allowing non-experts to create and modify sophisticated business applications quickly, making software development more agile and accessible '889 Patent, col. 5:1-10
Key Claims at a Glance
- The complaint reproduces independent claim 1 and seeks a declaration of its non-infringement Compl. ¶34
- The essential elements of independent claim 1 include:
- A system with processors, memory, and a "metadata database" for storing an application data element in a data serialization format.
- A "web service" configured to retrieve and parse the application data element.
- A "relational database of user data" configured to store the data element.
- Storage of metadata in a "dedicated repository" used to "dynamically arrange software code."
- A "set of backend processing elements" that convert metadata into user-defined behavior in real-time.
- An "intelligent data flow" that includes a series of specific steps, such as:
- A user request via HTTP REST API.
- Dynamic generation of SQL queries.
- Retrieval of metadata from a "NoSQL storage location."
- Dynamic generation of "C # code elements."
- Distribution of an event to a "distributed event bus."
- An event processing engine that dynamically generates "C # code elements" Compl. ¶34
III. The Accused Instrumentality
Product Identification
The accused instrumentality is the "SmartSuite work management platform," also referred to as the "SmartSuite Platform" Compl. ¶¶1 Compl. ¶20
Functionality and Market Context
- The SmartSuite Platform is a software-as-a-service (SaaS) product delivered via internet browsers and mobile applications Compl. ¶20
- It provides a configurable user interface that allows subscribers to create custom views, templates, and dashboards for work management Compl. ¶20 The complaint alleges it is a flexible platform for managing any process across various industries Compl. ¶19
- The complaint provides a marketing screenshot from the SmartSuite website, which depicts a dashboard-style user interface for managing project tasks Compl. ¶20, p. 6
IV. Analysis of Infringement Allegations
11,829,370 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a metadata database storing a plurality of application data elements in a data serialization format and a plurality of metadata structures... | SmartSuite argues it does not have the required dual-database architecture. The complaint contends that CodeBlox improperly mapped this element and the "user database" element to the same feature ("Tables") in SmartSuite's documentation. | ¶27 | col. 7:12-17 |
| a user database storing user data, wherein the user data comprising a plurality of user-defined values; | SmartSuite alleges its platform does not use a separate "user database" as claimed. It states that CodeBlox has not identified any such database, suggesting a structural mismatch with the claim. | ¶27 | col. 7:18-20 |
| wherein the web service allows for execution of the software code without using any software deployment processing comprising compilation, linking, installation, and configuration processes. | The complaint does not provide sufficient detail for analysis of this element. | ¶25 | col. 8:6-9 |
- Identified Points of Contention:
- Scope Questions: A primary point of contention is whether the claim terms "a metadata database" and "a user database" require two separate and distinct database systems. SmartSuite's non-infringement position hinges on the argument that its platform does not have this "dual-database architecture" Compl. ¶27
- Technical Questions: What evidence exists to show that the SmartSuite platform segregates storage of "application data elements and metadata structures" from "user-defined values" into two distinct databases as required by the claim language? The complaint alleges that CodeBlox has failed to identify any such architecture Compl. ¶27
11,269,889 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a metadata database configured to store an application data element in a data serialization format... | SmartSuite argues that the '889 patent requires a dual-database structure similar to the '370 patent, which its platform allegedly lacks. | ¶35 | col. 9:25-28 |
| a relational database of user data configured to store the data element in a table... | SmartSuite reiterates its non-infringement position based on the absence of a dual-database architecture ("metadata database and a relational database of user data"). | ¶35 | col. 10:6-8 |
| wherein an intelligent data flow includes... [a step where] a web service retrieves metadata structures relevant to the data being updated from a NoSQL storage location, | SmartSuite alleges that CodeBlox has not provided any evidence that its platform uses a "NoSQL storage location" for this purpose. | ¶35 | col. 10:27-28 |
| [wherein the intelligent data flow includes a step where] expressions defined in the metadata are used to dynamically generate C # code elements, | SmartSuite asserts that its platform does not perform this step and that CodeBlox has not alleged any facts to the contrary. | ¶35 | col. 11:1-2 |
| [wherein the intelligent data flow includes a step where] the C # code elements communicates with external systems and submits dynamically generated requests. | SmartSuite contends there is no allegation or evidence that its platform performs this specific function. | ¶35 | col. 11:23-24 |
- Identified Points of Contention:
- Scope Questions: Can the very specific claim recitation "C # code elements" be interpreted to cover other forms of dynamically generated or interpreted code (e.g., JavaScript), or is it strictly limited to the C# language? The complaint suggests a mismatch by noting CodeBlox failed to allege this element is practiced at all Compl. ¶35
- Technical Questions: Does the SmartSuite platform's architecture and operation align with the multi-step "intelligent data flow" detailed in claim 1? The complaint raises the question of whether there is any evidence that the platform performs specific claimed actions like using a NoSQL database for metadata retrieval or dynamically generating C# code Compl. ¶35
V. Key Claim Terms for Construction
'370 Patent
- The Term: "a metadata database" / "a user database"
- Context and Importance: The interpretation of these terms is critical, as SmartSuite's primary non-infringement argument for the '370 Patent is the absence of a "dual-database architecture" in its product Compl. ¶27 The case may turn on whether these terms require two structurally distinct databases or if they can be read on a single database with different logical partitions or tables.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: A party arguing for a broader definition might contend that "a database" can refer to a logical collection of data, and two such collections could exist within a single physical database instance. The specification does not explicitly forbid this.
- Evidence for a Narrower Interpretation: The use of the article "a" before each term ("a metadata database" and "a user database") in the same claim suggests two separate entities. This is strongly supported by Figure 1 in the incorporated '889 patent specification, which clearly depicts two separate database symbols labeled "Meta Data" (122) and "User Data" (120) '889 Patent, Fig. 1
'889 Patent
- The Term: "dynamically generate C # code elements"
- Context and Importance: This term is central to the highly detailed "intelligent data flow" recited in claim 1 of the '889 Patent. Practitioners may focus on this term because infringement will depend on whether the accused platform specifically generates C# code, as opposed to using another server-side technology or an interpretive model. SmartSuite identifies this as a feature for which CodeBlox has alleged no facts showing infringement Compl. ¶35
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent's abstract and detailed description refer to generating "underlying software code (e.g., C#, SQL, JavaScript, etc.)" '889 Patent, abstract '889 Patent, col. 4:22-24 The use of "e.g." (for example) suggests that C# is merely an exemplary, not exclusive, embodiment, potentially broadening the scope to other languages.
- Evidence for a Narrower Interpretation: While the specification provides a list of examples, claim 1 repeatedly and specifically recites "C # code elements" without the "e.g." qualifier '889 Patent, col. 11:1-24 The choice to select one specific language from the specification's list for inclusion in the claim may be interpreted as a deliberate narrowing of the claim's scope to that language only.
VI. Other Allegations
- Indirect Infringement: The complaint seeks a declaratory judgment of non-infringement with respect to contributory infringement and inducement Compl. p. 12, but it does not detail any specific factual allegations from CodeBlox that would form the basis for such claims.
- Willful Infringement: This section is not applicable, as the complaint is for declaratory judgment of non-infringement and does not contain allegations of willfulness.
VII. Analyst's Conclusion: Key Questions for the Case
- A core issue will be one of structural correspondence: does the SmartSuite platform's data storage architecture embody the "dual-database" structure (a distinct "metadata database" and "user database") that appears to be required by the claims of both the '370 and '889 patents and depicted in their shared specification?
- A key evidentiary question will be one of operational fidelity: does the accused platform's runtime behavior match the highly specific, multi-step "intelligent data flow" claimed in the '889 patent, particularly the requirements to "dynamically generate C # code elements" and retrieve metadata from a "NoSQL storage location"?
Analysis metadata
Loading Complaint
Suggested improvements