| May 5, 2026 06:38 UTC | October 16, 2026 01:01 UTC | ||||
|---|---|---|---|---|---|
| n | 1 | Team accounts with unlimited members now available to everyone! Invite your team | n | 1 | Neon now has realtime: Live SQL with full reactivity. Try it in Beta today |
| > | mates and ship faster together, even on the Free Plan. | ||||
| 2 | Neon | 2 | Neon | ||
| 3 | Product | 3 | Product | ||
| 4 | Solutions | 4 | Solutions | ||
| 5 | Docs | 5 | Docs | ||
| 6 | Pricing | 6 | Pricing | ||
| 7 | Resources | 7 | Resources | ||
| n | n | 8 | Core PrimitivesLakebase PostgresServerless Postgres database | ||
| 9 | Object StorageS3-compatible storage that branches | ||||
| 10 | FunctionsServerless compute next to your data | ||||
| 11 | RealtimeLive SQL queries and reactive DX | ||||
| 12 | Managed Better AuthAuthentication built into your database | ||||
| 13 | AI GatewayOne API for frontier and open-source models | ||||
| 8 | Core DatabaseNeon's lakebase architectureStorage-compute separation. | 14 | FeaturesLakebase ArchitectureStorage-compute separation | ||
| 9 | AutoscalingAutomatic instance sizing | 15 | AutoscalingAutomatic instance sizing | ||
| n | 10 | Read ReplicasInstant, autoscaling replicas | n | 16 | BranchingFaster Postgres workflows |
| 17 | SearchVector, keyword, and hybrid search | ||||
| 11 | Instant RestoreInstant recovery when mistakes happen | 18 | Instant RestoreInstant recovery when mistakes happen | ||
| n | 12 | Built-In FeaturesDatabase BranchesFaster Postgres workflows | n | ||
| 13 | AuthenticationAuth for your App, built in to your DB | ||||
| 14 | Data APIREST HTTP API for your database | ||||
| 15 | Connection PoolingEfficiently manage database connections | ||||
| 16 | What is Neon | 19 | What is Neon | ||
| n | 17 | Serverless Postgres, by Databricks | n | 20 | Built around Lakebase Postgres, by Databricks |
| 18 | Use casesServerless AppAutoscale with traffic | 21 | Use casesFull-stack appsDeploy backends via your agent | ||
| 19 | Multi-TBScale and restore instantly | 22 | Branching workflowsSimplify DB ops to ship faster & safer | ||
| 20 | Database per tenantData isolation without overhead | 23 | Bursty workloadsAvoid overprovisioning & optimize performance | ||
| 21 | Build & operatePlatformsOffer Postgres for your users | 24 | Large databasesRestore & replicate your DB in seconds | ||
| 22 | Dev/TestsProduction-like environment | 25 | Deploy at scaleAgents | ||
| 23 | AgentsBuild full-stack AI agents | 26 | Infra for app-generation agents like Replit & v0 | ||
| 27 | AI | ||||
| 28 | Platforms | ||||
| 29 | Deploy isolated backends for your end users | ||||
| 24 | LearnBlogTechnical posts & product updates | 30 | LearnBlogTechnical posts & product updates | ||
| 25 | Case studiesExplore customer stories | 31 | Case studiesExplore customer stories | ||
| 26 | ChangelogProduct updates | 32 | ChangelogProduct updates | ||
| 33 | StatusService status | 39 | StatusService status | ||
| 34 | Discord21.5k | 40 | Discord21.5k | ||
| 35 | Log inSign up | 41 | Log inSign up | ||
| n | 36 | Neon Platform Services Product Specific Schedule | n | 42 | Product Specific Schedule (Neon) |
| 37 | This Neon Platform Services Product Specific Schedule ("Product Specific Schedul | 43 | Last Updated: October 14, 2026 | ||
| > | e") is entered into as of the Effective Date between Neon, LLC ("Neon" or "we"), | ||||
| > | an affiliate of Databricks, Inc. ("Databricks"), and Customer (as defined below | ||||
| > | ) ("Customer", "you," or "your") and governs Customer's use of the Neon propriet | ||||
| > | ary cloud computing platform services (the "Neon Platform Services"). By accessi | ||||
| > | ng the Neon Platform Services, Customer agrees to the terms of this Product Spec | ||||
| > | ific Schedule. If you are entering into this Product Specific Schedule on behalf | ||||
| > | of a company (such as your employer) or other legal entity, you represent and w | ||||
| > | arrant that you are authorized to bind that entity to this Product Specific Sche | ||||
| > | dule, in which case "Customer," "you," or "your" will refer to that entity (othe | ||||
| > | rwise, such terms refer to you as an individual). | ||||
| 38 | This Product Specific Schedule is subject to the terms of the current Databricks | 44 | This Product Specific Schedule (Neon) (this "Schedule") is entered into as of th | ||
| > | Master Cloud Services Agreement located at https://www.databricks.com/legal/mcs | > | e Effective Date between Databricks, Inc., the parent company of Neon, LLC ("Dat | ||
| > | a (the "Agreement"), as supplemented and amended by this Product Specific Schedu | > | abricks"), and Customer and governs Customer's use of Databricks' Neon product f | ||
| > | le, solely with respect to a Customer's use of the Neon Platform Services. Custo | > | amily of cloud computing platform services, as described in the Documentation (t | ||
| > | mer acknowledges that we may make changes to the Agreement, this Product Specifi | > | he "Platform Services", for purposes of this Schedule). By accessing the Platfor | ||
| > | c Schedule or pricing from time to time and Customer's continued use of the Neon | > | m Services, Customer agrees to the terms of this Schedule. If you are entering i | ||
| > | Platform Services will constitute consent to such changes. | > | nto this Schedule on behalf of a company (such as your employer) or other legal | ||
| > | entity, you represent and warrant that you are authorized to bind that entity to | ||||
| > | this Schedule, in which case "Customer" will refer to that entity (otherwise, " | ||||
| > | Customer" refers to you as an individual). | ||||
| 39 | For clarity, this Product Specific Schedule does not affect the terms of the Agr | 45 | This Schedule is subject to the terms of the then-current Databricks Master Clou | ||
| > | eement as they relate to any non-Neon Platform Services, including the Databrick | > | d Services Agreement located at https://www.databricks.com/legal/mcsa (the "Agre | ||
| > | s data processing platform services. Capitalized terms not defined here will hav | > | ement"), as supplemented and amended by this Schedule, solely with respect to a | ||
| > | e the meanings specified in the Agreement. For purposes of this Product Specific | > | Customer's use of the Platform Services. Customer acknowledges that Databricks m | ||
| > | Schedule, all references under the Agreement to the "Platform Services" and the | > | ay make changes to the Agreement, this Schedule, and pricing from time to time, | ||
| > | "Databricks Services" will be deemed references to the "Neon Platform Services" | > | and Customer's continued use of the Platform Services will constitute consent to | ||
| > | , and all references to "Databricks" under the Agreement will be deemed referenc | > | such changes. | ||
| > | es to "Databricks, together with its Affiliates". In the event of any conflict o | ||||
| > | r inconsistency between this Product Specific Schedule and the Agreement, solely | ||||
| > | with respect to Customer's use of Neon Platform Services, this Product Specific | ||||
| > | Schedule will control. | ||||
| 46 | For clarity, this Schedule does not affect the terms of the Agreement as they re | ||||
| > | late to services provided by or on behalf of Databricks other than Platform Serv | ||||
| > | ices. Capitalized terms not defined here will have the meanings specified in the | ||||
| > | Agreement. For purposes of this Schedule, all references under the Agreement to | ||||
| > | the "Platform Services" and the "Databricks Services" will be deemed references | ||||
| > | to the "Platform Services" as defined in this Schedule. In the event of any con | ||||
| > | flict or inconsistency between this Schedule and the Agreement, solely with resp | ||||
| > | ect to Customer's use of the Platform Services, this Schedule will control. | ||||
| 40 | Self-Service Plans. The Neon Platform Services will be provided according to the | 47 | Self-Service Plans. The Platform Services will be provided according to the usag | ||
| > | usage-based pricing plan selected by Customer, as described in the Documentatio | > | e-based pricing plan selected by Customer, as described in the Documentation at | ||
| > | n at https://neon.com/docs/introduction/plans (such plans, together with any leg | > | https://neon.com/docs/introduction/plans, or successor URL (such plans, together | ||
| > | acy plans, a "Self Service Plan"). Customer's subscription to any Self Service P | > | with any legacy plans, a "Self Service Plan"). Customer's subscription to any S | ||
| > | lan will automatically renew on a month-to-month basis (each, a "Subscription Mo | > | elf Service Plan will automatically renew on a month-to-month basis (each, a "Su | ||
| > | nth"), unless Customer cancels its subscription to such Self Service Plan within | > | bscription Month"), unless Customer cancels its subscription to such Self Servic | ||
| > | fourteen (14) business days prior to the expiration of the then-current Subscri | > | e Plan within fourteen (14) business days prior to the expiration of the then-cu | ||
| > | ption Month. | > | rrent Subscription Month. | ||
| 41 | Fees. Except as otherwise specified in an Order Form, (a) Fees will be determine | 48 | Fees. Fees will be billed by Databricks (or its affiliate, Neon, LLC on Databric | ||
| > | d based on the Self Service Plan selected by Customer and calculated based on Cu | > | ks' behalf). Except as otherwise specified in an Order, Fees (a) will be determi | ||
| > | stomer's usage of the Neon Platform Services during each Subscription Month, and | > | ned based on the Self Service Plan selected by Customer and calculated based on | ||
| > | (b) all Fees will be invoiced monthly in arrears with payment invoiced and due | > | Customer's usage of the Platform Services during each Subscription Month, (b) wi | ||
| > | on or around the first day of the calendar month following each Subscription Mon | > | ll be invoiced monthly in arrears with payment invoiced and due on or around the | ||
| > | th. Fees will be automatically charged to Customer's payment card on record. | > | first day of the calendar month following each Subscription Month, and (c) will | ||
| > | be automatically charged to Customer's payment card on record. | ||||
| 42 | Amendments to the Agreement: | 49 | Amendments to the Agreement: | ||
| n | 43 | Documentation. All references in the Agreement to the "Documentation" shall be d | n | 50 | Documentation. All references in the Agreement to the "Documentation" shall be d |
| > | eemed references to the documentation related to the Neon Platform Services loca | > | eemed references to the documentation related to the Platform Services located a | ||
| > | ted at https://neon.com/docs. | > | t https://neon.com/docs. | ||
| 44 | Subprocessor List. All references in the Agreement (including, for clarity, Sect | 51 | Subprocessor List. The Platform Services use Grafana Labs located in the United | ||
| > | ion 4 of the DPA) to the "Subprocessor List" shall be deemed references to the s | > | States for infrastructure services in addition to all other listed subprocessors | ||
| > | ubprocessor list specific to the Neon Platform Services located at https://neon. | > | located at https://www.databricks.com/legal/databricks-subprocessors. | ||
| > | com/subprocessors. | ||||
| 45 | Security Addendum. All references in the Agreement to the "Security Addendum" or | 52 | Security Addendum. All references in the Agreement to the "Security Addendum" or | ||
| > | "Security Measures" shall be deemed references to the security addendum and sec | > | "Security Measures" shall be deemed references to the security addendum and sec | ||
| > | urity measures attached hereto as Exhibit A. | > | urity measures attached hereto as Exhibit A. | ||
| n | 46 | Audit. Section 7 (Audits and Records) of the DPA is hereby deleted in its entire | n | 53 | Audit. Section 7 (Audits and Records) of the DPA is hereby deleted in its entire |
| > | ty and replaced with the following: "Databricks, together with its Affiliates, w | > | ty and replaced with the following: "Databricks, together with its Affiliates, w | ||
| > | ill make information reasonably necessary to demonstrate compliance with this DP | > | ill make information reasonably necessary to demonstrate compliance with this DP | ||
| > | A available to Customer and allow for and contribute to audits, including inspec | > | A available to Customer and allow for and contribute to audits, including inspec | ||
| > | tions conducted by Customer or Customer's auditor in order to assess compliance | > | tions conducted by Customer or Customer's auditor in order to assess compliance | ||
| > | with this DPA, where required by applicable law. Customer acknowledges and agree | > | with this DPA, where required by applicable law. Customer acknowledges and agree | ||
| > | s that Customer will exercise Customer's audit rights under this DPA by instruct | > | s that Customer will exercise Customer's audit rights under this DPA by instruct | ||
| > | ing us to comply with the audit measures described in this provision. Upon reque | > | ing us to comply with the audit measures described in this provision. Upon reque | ||
| > | st, Databricks, together with its Affiliates, will supply (on a confidential bas | > | st, Databricks, together with its Affiliates, will supply (on a confidential bas | ||
| > | is) the SOC 2 report for the Neon Platform Services and summary copies of the pe | > | is) the SOC 2 report for the Platform Services and summary copies of the penetra | ||
| > | netration testing report(s) to Customer so that Customer can verify compliance w | > | tion testing report(s) to Customer so that Customer can verify compliance with t | ||
| > | ith this DPA." | > | his DPA." | ||
| 47 | Service Specific Terms. All references in the Agreement to the Service Specific | 54 | Service Specific Terms. All references in the Agreement to the Service Specific | ||
| > | Terms are hereby deleted. | > | Terms are hereby deleted. | ||
| n | 48 | Projects. All references in the Agreement to "Workspaces" shall be deemed to inc | n | 55 | Projects. All references in the Agreement to "Workspaces" shall be deemed to inc |
| > | lude any projects created by Customer within the Neon Platform Services. | > | lude any projects created by Customer within the Platform Services. | ||
| 49 | Cardholder Data. Customer acknowledges and agrees it shall not include in Custom | 56 | Cardholder Data. Customer acknowledges and agrees it shall not include in Custom | ||
| > | er Content any cardholder data as defined under PCI-DSS ("Cardholder Data"). All | > | er Content any cardholder data as defined under PCI-DSS. | ||
| > | references to Cardholder Data in Section 4.5(b) shall be hereby deleted. | ||||
| 50 | SLA. Notwithstanding anything to the contrary, the Service Level Agreement locat | 57 | Externally-hosted TypeSafe Models. Customers may choose to instruct Databricks t | ||
| > | ed at https://neon.com/neon-business-sla shall be incorporated into this Product | > | o facilitate Customer's access to and use of models hosted and offered by TypeSa | ||
| > | Specific Schedule by reference and apply exclusively to Customers who have subs | > | fe AI, Inc. ("Externally-hosted TypeSafe Models") in connection with the Platfor | ||
| > | cribed to the Scale self-service plan. | > | m Services. Externally-hosted TypeSafe Models are Non-Databricks Offerings under | ||
| > | the Agreement. Customer acknowledges and agrees that its access to and use of E | ||||
| > | xternally-hosted TypeSafe Models, and TypeSafe AI's processing of any data Custo | ||||
| > | mer submits to or receives from TypeSafe AI in connection with such access and u | ||||
| > | se, are governed solely by TypeSafe's terms and conditions (including its data p | ||||
| > | rocessing addendum) and privacy policy, and not the Agreement. | ||||
| 58 | SLA. Notwithstanding anything to the contrary, the Service Level Agreement locat | ||||
| > | ed at https://neon.com/neon-business-sla shall be incorporated into this Schedul | ||||
| > | e by reference and apply exclusively to Customers who have subscribed to the Sca | ||||
| > | le Self Service Plan. | ||||
| 51 | Exhibit A -- Security Measures | 59 | Exhibit A -- Security Measures | ||
| n | 52 | Neon, together with its Affiliate Databricks, shall implement reasonable adminis | n | 60 | Databricks, shall implement reasonable administrative, physical, and technical s |
| > | trative, physical, and technical safeguards to protect the security of the Neon | > | afeguards to protect the security of the Platform Services and the Customer Cont | ||
| > | Platform Services and the Customer Content as set forth in this Exhibit A ("Secu | > | ent as set forth in this Exhibit A ("Security Measures"). While Databricks may u | ||
| > | rity Measures"). While Neon may update the Security Measures, it shall not mater | > | pdate the Security Measures, it shall not materially diminish the effectiveness | ||
| > | ially diminish the effectiveness of the Security Measures during the Term of an | > | of the Security Measures during the term of an Order. All capitalized terms not | ||
| > | Order. All capitalized terms not otherwise defined herein will have the meanings | > | otherwise defined herein will have the meanings as set forth in the Agreement. | ||
| > | as set forth in the Agreement. | ||||
| 53 | Access Control. | 61 | Access Control. | ||
| 54 | Preventing Unauthorized Product Access | 62 | Preventing Unauthorized Product Access | ||
| n | 55 | Outsourced processing. We host the Neon Platform Services on an outsourced cloud | n | 63 | Outsourced processing. Databricks hosts the Platform Services on an outsourced c |
| > | infrastructure provider, according to a shared responsibility model. | > | loud infrastructure provider, according to a shared responsibility model. | ||
| 56 | Physical and environmental security. We host our product infrastructure with mul | 64 | Physical and environmental security. Databricks hosts our product infrastructure | ||
| > | ti-tenant, outsourced infrastructure providers. We do not own or maintain hardwa | > | with multi-tenant, outsourced infrastructure providers. Databricks does not own | ||
| > | re located at the outsourced infrastructure providers' data centers. Production | > | or maintain hardware located at the outsourced infrastructure providers' data c | ||
| > | servers and client-facing applications are logically and physically secured from | > | enters. Production servers and client-facing applications are logically and phys | ||
| > | our internal corporate information systems. | > | ically secured from our internal corporate information systems. | ||
| 57 | Authentication. We implement a uniform authentication policy for our customer pr | 65 | Authentication. Databricks implements a uniform authentication policy for our cu | ||
| > | oducts. Customers who interact with the products via the user interface must aut | > | stomer products. Customers who interact with the products via the user interface | ||
| > | henticate before accessing Customer Content. | > | must authenticate before accessing Customer Content. | ||
| 58 | Authorization. Customer Content is stored in multi-tenant storage systems access | 66 | Authorization. Customer Content is stored in multi-tenant storage systems access | ||
| > | ible to Customers via only application user interfaces and application programmi | > | ible to Customers via only application user interfaces and application programmi | ||
| > | ng interfaces. Customers are not allowed direct access to the underlying applica | > | ng interfaces. Customers are not allowed direct access to the underlying applica | ||
| > | tion infrastructure. The authorization model in each of our products is designed | > | tion infrastructure. The authorization model in each of our products is designed | ||
| > | to ensure that only the appropriately assigned individuals can access relevant | > | to ensure that only the appropriately assigned individuals can access relevant | ||
| > | features, views, and customization options. Authorization to data sets is perfor | > | features, views, and customization options. Authorization to data sets is perfor | ||
| > | med through validating the user's permissions against the attributes associated | > | med through validating the user's permissions against the attributes associated | ||
| > | with each data set. | > | with each data set. | ||
| 59 | Application Programming Interface (API) access: Public product APIs can be acces | 67 | Application Programming Interface (API) access: Public product APIs can be acces | ||
| > | sed using an API key or through Oauth authorization. | > | sed using an API key or through Oauth authorization. | ||
| n | 60 | Preventing Unauthorized Use. We implement industry standard access controls and | n | 68 | Preventing Unauthorized Use. Databricks implements industry standard access cont |
| > | detection capabilities for the internal networks that support its products. | > | rols and detection capabilities for the internal networks that support its produ | ||
| > | cts. | ||||
| 61 | Access controls. Network access control mechanisms are designed to prevent netwo | 69 | Access controls. Network access control mechanisms are designed to prevent netwo | ||
| > | rk traffic using unauthorized protocols from reaching the product infrastructure | > | rk traffic using unauthorized protocols from reaching the product infrastructure | ||
| > | . The technical measures implemented differ between infrastructure providers and | > | . The technical measures implemented differ between infrastructure providers and | ||
| > | include Virtual Private Cloud (VPC) implementations, security group assignment, | > | include Virtual Private Cloud (VPC) implementations, security group assignment, | ||
| > | and traditional firewall rules. | > | and traditional firewall rules. | ||
| n | 62 | Intrusion detection and prevention. We implement a Web Application Firewall (WAF | n | 70 | Intrusion detection and prevention. Databricks implements a Web Application Fire |
| > | ) solution to protect hosted customer websites and other internet-accessible app | > | wall (WAF) solution to protect hosted customer websites and other internet-acces | ||
| > | lications. The WAF is designed to identify and prevent attacks against publicly | > | sible applications. The WAF is designed to identify and prevent attacks against | ||
| > | available network services. | > | publicly available network services. | ||
| 63 | Static code analysis. Code stored in our source code repositories is checked for | 71 | Static code analysis. Code stored in our source code repositories is checked for | ||
| > | best practices and identifiable software flaws using automated tooling. | > | best practices and identifiable software flaws using automated tooling. | ||
| n | 64 | Penetration testing. We maintain relationships with industry-recognized penetrat | n | 72 | Penetration testing. Databricks maintains relationships with industry-recognized |
| > | ion testing service providers for penetration testing of the Neon web applicatio | > | penetration testing service providers for penetration testing of the Neon web a | ||
| > | n, API, and proximity and authentications flows at least annually. The intent of | > | pplication, API, and proximity and authentications flows at least annually. The | ||
| > | these penetration tests is to identify security vulnerabilities and mitigate th | > | intent of these penetration tests is to identify security vulnerabilities and mi | ||
| > | e risk and business impact they pose to the in-scope systems. | > | tigate the risk and business impact they pose to the in-scope systems. | ||
| 65 | Limitations of Privilege & Authorization Requirements. | 73 | Limitations of Privilege & Authorization Requirements. | ||
| 66 | Product access. A subset of our employees have access to the products and to cus | 74 | Product access. A subset of our employees have access to the products and to cus | ||
| > | tomer data via controlled interfaces. The intent of providing access to a subset | > | tomer data via controlled interfaces. The intent of providing access to a subset | ||
| > | of employees is to provide effective customer support, product development and | > | of employees is to provide effective customer support, product development and | ||
| > | research, to troubleshoot potential problems, to detect and respond to security | > | research, to troubleshoot potential problems, to detect and respond to security | ||
| > | incidents and implement data security. Access is enabled through "just in time" | > | incidents and implement data security. Access is enabled through "just in time" | ||
| > | (JITA) requests for access; all such requests are logged. Employees are granted | > | (JITA) requests for access; all such requests are logged. Employees are granted | ||
| > | access by role, and reviews of high risk privilege grants are initiated as neede | > | access by role, and reviews of high risk privilege grants are initiated as neede | ||
| > | d. Administrative or high risk access permissions are reviewed at least annually | > | d. Administrative or high risk access permissions are reviewed at least annually | ||
| > | . | > | . | ||
| n | 67 | Reference checks. Where permitted by applicable law, Databricks and Neon employe | n | 75 | Reference checks. Where permitted by applicable law, employees of Databricks and |
| > | es undergo reference checks. All Databricks and Neon employees are required to c | > | our affiliates undergo reference checks. All employees are required to conduct | ||
| > | onduct themselves in a manner consistent with company guidelines, non-disclosure | > | themselves in a manner consistent with company guidelines, non-disclosure requir | ||
| > | requirements, and ethical standards. | > | ements, and ethical standards. | ||
| 68 | Transmission Control | 76 | Transmission Control | ||
| n | 69 | In-transit. We require HTTPS encryption (also referred to as SSL or TLS) on all | n | 77 | In-transit. Databricks requires HTTPS encryption (also referred to as SSL or TLS |
| > | login interfaces. Our HTTPS implementation uses industry standard algorithms and | > | ) on all login interfaces. Our HTTPS implementation uses industry standard algor | ||
| > | certificates. | > | ithms and certificates. | ||
| 70 | At-rest. We store user passwords following policies that follow industry standar | 78 | At-rest. Databricks stores user passwords following policies that follow industr | ||
| > | d practices for security. We have implemented technologies to ensure that stored | > | y standard practices for security. Databricks has implemented technologies to en | ||
| > | data is encrypted at rest. | > | sure that stored data is encrypted at rest. | ||
| 71 | Input Control. | 79 | Input Control. | ||
| n | 72 | Detection. We designed our infrastructure to log extensive information about the | n | 80 | Detection. Databricks designed our infrastructure to log extensive information a |
| > | system behavior, traffic received, system authentication, and other application | > | bout the system behavior, traffic received, system authentication, and other app | ||
| > | requests. Internal systems aggregate log data and alert appropriate employees o | > | lication requests. Internal systems aggregate log data and alert appropriate emp | ||
| > | f malicious, unintended, or anomalous activities. Our personnel, including secur | > | loyees of malicious, unintended, or anomalous activities. Our personnel, includi | ||
| > | ity, operations, and support personnel, are responsive to known incidents. | > | ng security, operations, and support personnel, are responsive to known incident | ||
| > | s. | ||||
| 73 | Response and tracking. We maintain a record of known security incidents that inc | 81 | Response and tracking. Databricks maintains a record of known security incidents | ||
| > | ludes description, dates and times of relevant activities, and incident disposit | > | that includes description, dates and times of relevant activities, and incident | ||
| > | ion. Suspected and confirmed security incidents are investigated by security, op | > | disposition. Suspected and confirmed security incidents are investigated by sec | ||
| > | erations, or support personnel; and appropriate resolution steps are identified | > | urity, operations, or support personnel; and appropriate resolution steps are id | ||
| > | and documented. For any confirmed incidents, we will take appropriate steps to m | > | entified and documented. For any confirmed incidents, Databricks will take appro | ||
| > | inimize product and Customer damage or unauthorized disclosure. Notification to | > | priate steps to minimize product and Customer damage or unauthorized disclosure. | ||
| > | you will be in accordance with the terms of the Agreement. | > | Notification to Customer will be in accordance with the terms of the Agreement. | ||
| 74 | Availability Control. | 82 | Availability Control. | ||
| 75 | Online replicas and backups. Where feasible, production databases are designed t | 83 | Online replicas and backups. Where feasible, production databases are designed t | ||
| > | o replicate data between no less than 1 primary and 1 secondary database. All da | > | o replicate data between no less than 1 primary and 1 secondary database. All da | ||
| > | tabases are backed up and maintained using at least industry standard methods. | > | tabases are backed up and maintained using at least industry standard methods. | ||
| n | 76 | Disaster Recovery Plans. We maintain and regularly test disaster recovery plans | n | 84 | Disaster Recovery Plans. Databricks maintains and regularly test disaster recove |
| > | to help ensure availability of information following interruption to, or failure | > | ry plans to help ensure availability of information following interruption to, o | ||
| > | of, critical business processes. | > | r failure of, critical business processes. | ||
| 77 | Our products are designed to ensure redundancy and seamless failover. The server | 85 | Our products are designed to ensure redundancy and seamless failover. The server | ||
| > | instances that support the products are also architected with a goal to prevent | > | instances that support the products are also architected with a goal to prevent | ||
| > | single points of failure. This design assists our operations in maintaining and | > | single points of failure. This design assists our operations in maintaining and | ||
| > | updating the product applications and backend while limiting downtime. | > | updating the product applications and backend while limiting downtime. | ||
| n | 78 | Neon | n | 86 | Neon is part of the Databricks Platform |
| 79 | A Databricks Company | ||||
| 80 | Neon status loading...© Neon 2026. All rights reserved. Apache, Apache Spark, Sp | 87 | © Neon 2026. All rights reserved. Apache, Apache Spark, Spark, the Spark Logo, A | ||
| > | ark, the Spark Logo, Apache Iceberg, Iceberg, and the Apache Iceberg logo are tr | > | pache Iceberg, Iceberg, and the Apache Iceberg logo are trademarks of the Apache | ||
| > | ademarks of the Apache Software Foundation. | > | Software Foundation. | ||
| 81 | Privacy NoticeTerms of UseNeon Platform TermsModern Slavery StatementCalifornia | ||||
| > | Privacy | ||||
| 82 | CompanyAbout | 88 | CompanyAbout | ||
| 83 | Blog | 89 | Blog | ||
| 84 | Careers | 90 | Careers | ||
| 104 | HIPAACompliantCompliance Guide | 110 | HIPAACompliantCompliance Guide | ||
| 105 | Neon’s Sub Contractors | 111 | Neon’s Sub Contractors | ||
| 106 | Trust Center | 112 | Trust Center | ||
| t | t | 113 | Neon status loading...Privacy NoticeTerms of UseNeon Platform TermsModern Slaver | ||
| > | y StatementCalifornia Privacy | ||||
Follow unlimited companies, monitor the clauses that matter across every platform, and get the full institutional analysis on what each change obligates you to do.