dvilasuero HF staff commited on
Commit
edb05f6
1 Parent(s): 36c4b3b

Upload argilla_cloud.txt

Browse files
Files changed (1) hide show
  1. argilla_cloud.txt +134 -0
argilla_cloud.txt ADDED
@@ -0,0 +1,134 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+
2
+ This documents an overview of the Argilla Cloud service - a comprehensive Software as a Service (SaaS) solution for data labeling and curation.
3
+
4
+ The service is specifically designed to meet the needs of businesses seeking a reliable, secure, and user-friendly platform for data management. The key components of our service include advanced security measures, robust data backup and recovery protocols, flexible pricing options, and dedicated customer support. The onboarding process is efficient, enabling clients to start using the service within one business day. The scope of this proposal includes details on the aforementioned aspects, providing a clear understanding of the service offerings and associated processes.
5
+
6
+ Argilla Cloud offers four plans:
7
+
8
+ Starter: Ideal for teams initiating their journey in scaling data curation and labelling projects. Perfect for environments where production monitoring is not a requirement.
9
+ Base: Tailored for teams seeking to amplify their data curation, labelling efforts, and model monitoring, with enhanced support from Argilla.
10
+ Medium: Designed for teams expanding their language model pipelines, requiring robust ML lifecycle management fortified by Argilla's comprehensive support.
11
+ Large: Geared towards teams heavily dependent on language model pipelines, human feedback, and applications, requiring complete ML lifecycle management with robust support.
12
+
13
+ Scope of services
14
+ Argilla Cloud, a fully managed SaaS, encompasses the following functionalities:
15
+ Unrestricted Users, Datasets, and Workspaces: The service imposes no limits on the number of users, datasets, or workspaces, supporting scalability of operations.
16
+ Role-Based Access Control: Administrators and annotators have differentiated access rights to ensure structured and secure data management.
17
+ Custom Subdomain: Clients are provided with a distinct argilla.io subdomain for accessing the platform.
18
+ Regular Updates and Upgrades: The service includes regular platform patches and upgrades as part of routine maintenance to uphold system integrity and security.
19
+ Managed Service: Infrastructure maintenance, backend operations, and other technical aspects are managed by Argilla, eliminating the need for client-side management.
20
+
21
+
22
+
23
+ Security
24
+ The security framework of the Argilla Cloud service involves a multi-faceted approach:
25
+ Data Encryption at Rest: Data stored within the system is encrypted, forming a crucial layer of security. This process automatically encrypts data prior to storage, guarding against unauthorized access.
26
+ Network Security Measures: The infrastructure has been designed to prevent unauthorized intrusion and to ensure consistent service availability. Measures include firewall protections, intrusion detection systems, and scheduled vulnerability scans to detect and address potential threats.
27
+ Role-Based Access Control: The system implements role-based access control, defining access levels based on user roles. This mechanism controls the extent of access to sensitive information, aligning it with the responsibilities of each role.
28
+ Security Audits: Regular audits of security systems and protocols are conducted to detect potential vulnerabilities and verify adherence to security standards.
29
+ Employee Training: All personnel receive regular security training, fostering an understanding of the latest threats and the importance of security best practices.
30
+ Incident Response Protocol: In the case of a security incident, a pre-defined incident response plan is activated. This plan outlines the procedures for managing different types of security events, and aims to ensure swift mitigation of potential damage.
31
+ In summary, the security measures in place include data encryption, network security protocols, role-based access control, regular audits, employee training, and a comprehensive incident response plan. These measures contribute to a secure environment for data management.
32
+
33
+
34
+ Setup and onboarding
35
+ The process for setup and onboarding for Argilla Cloud is designed to be efficient and straightforward. The procedure involves a sequence of steps to ensure a smooth transition and optimal use of the service.
36
+
37
+ Step 1: Account Creation
38
+ The setup process begins with the creation of the client owner account. We require the client to provide the following details:
39
+ Full name of the administrator
40
+ Preferred username
41
+ Administrator's email address
42
+ Once these details are received, we send an onboarding email to sign up.
43
+
44
+ Step 2: Platform Orientation
45
+ Once logged in, the administrator has full access to the Argilla Cloud platform. They can familiarize themselves with the platform interface and various features. If required, a guided tour or tutorial can be provided to walk the administrator through the platform.
46
+
47
+ Step 3: User Management
48
+ The administrator is then responsible for setting up additional user accounts. They can invite users via email, manage roles (admin, annotator, etc.), and assign access permissions to different workspaces and datasets.
49
+
50
+ Step 4: Workspace and Dataset Configuration
51
+ The administrator can create and manage multiple workspaces and datasets. They have the option to configure settings as per their team's requirements, including assigning datasets to specific workspaces and managing access permissions.
52
+
53
+ Step 5: Training and Support
54
+ Argilla provides open resources and support to aid in the onboarding process. This includes user manuals, tutorials, and access to our support team for any queries or issues that may arise during the setup and onboarding process.
55
+ By following these steps, new users can be quickly onboarded and begin using the Argilla Cloud service with minimal downtime. This process ensures the client administrator has full control over their team's access and can manage their workspace efficiently.
56
+
57
+ Plans
58
+ The plans for the Argilla Cloud service depend on the volume of records processed, with several tiers available to suit varying needs. Each tier has a corresponding monthly and annual price, with a 10% discount applied to the annual pricing option. The tier selection and associated price will be determined by the client's selection in the Service Order Form section of the Terms of Service document.
59
+ Plans are:
60
+ Starter 1 Million records
61
+ Base 3 Million records
62
+ Medium 4 Million records
63
+ Large 6 million records
64
+
65
+
66
+ Support
67
+ Argilla Cloud offers comprehensive support services to address various issues that may arise during the use of our service. Support levels are categorized into four distinct tiers, based on the severity of the issue, and a separate category for feature requests. The support process, response times, and procedures differ for each category.
68
+ (1) Critical Issues
69
+ Critical issues are characterized by:
70
+ Severe impact on the Service, potentially rendering it completely non-functional.
71
+ Disruption of critical service operations or functions.
72
+ Obstruction of entire customer workflows.
73
+ In the case of a critical issue, Argilla will:
74
+ Assign specialist(s) to correct the issue on an expedited basis.
75
+ Provide ongoing communication on the status via email and/or phone, according to the customer's preference.
76
+ Begin work towards identifying a temporary workaround or fix.
77
+ (2) Major Issues
78
+ Major issues involve:
79
+ Limited functionality of the Service.
80
+ Service instability with periodic interruptions.
81
+ Material service interruptions in mission-critical functions.
82
+ Time-sensitive questions impacting performance or deliverables to end-clients.
83
+ Upon encountering a major issue, Argilla will:
84
+ Assign a specialist to begin a resolution.
85
+ Implement additional, escalated procedures as reasonably determined necessary by Argilla Support Services staff.
86
+ (3) Minor Issues
87
+ Minor issues include:
88
+ Errors causing partial, non-critical functionality loss.
89
+ The need for clarification on procedures or information in documentation.
90
+ Errors in service that may impact performance deliverables.
91
+ (4) Trivial Issues
92
+ Trivial issues are characterized by:
93
+ Errors in system development with little to no impact on performance.
94
+ Feature Requests
95
+ Feature requests involve:
96
+ Requesting a product enhancement.
97
+ For feature requests, Argilla will:
98
+ Respond regarding the relevance and interest in incorporating the requested feature.
99
+ In summary, Argilla Cloud's support services are designed to provide timely and efficient assistance for issues of varying severity, ensuring a smooth and reliable user experience.
100
+ All plans include Monday to Friday during office hours (8am to 17pm CEST) with additional support upon request.
101
+
102
+
103
+ The Support Channels and features of each tier are shown below:
104
+
105
+ Starter: Slack Community. Severity 1 - Response time < 4 hours. Severity 2 - Response time < 8 hours. Severity 3 - Response time < 48 hours. Severity 4 not specified.
106
+
107
+ Base: Ticketing System, Severity 1 - Response time < 4 hours. Severity 2 - Response time < 8 hours. Severity 3 - Response time < 24 hours. Severity 4 not specified.
108
+
109
+ Medium: Ticketing System and dedicated Slack channel, Severity 1 - Response time < 4 hours. Severity 2 - Response time < 8 hours. Severity 3 - Response time < 24 hours. Severity 4 one week
110
+
111
+ Large: Ticketing System and dedicated Slack channel, Severity 1 - Response time < 4 hours. Severity 2 - Response time < 8 hours. Severity 3 - Response time < 24 hours. Severity 4 one week.
112
+
113
+
114
+
115
+ Data backup and recovery plan
116
+ Argilla Cloud is committed to ensuring the safety and availability of your data. Our system is designed to run six data backups per day as a standard procedure. These backups capture a snapshot of the system state at the time of the backup, enabling restoration to that point if necessary.
117
+ Our Recovery Point Objective (RPO) is four hours. This means that in the event of a system failure, the maximum data loss would be up to the last four hours of data input. We achieve this by running regular backups throughout the day, reducing the time window of potential data loss.
118
+ Our Recovery Time Objective (RTO) is one hour. This is the maximum acceptable length of time that your system could be down following a failure or disruption. It represents our commitment to ensuring that your services are restored as quickly as possible.
119
+ In the event of a disruption, our team will first evaluate the issue to determine the best course of action. If data recovery is necessary, we will restore from the most recent backup. We will then work to identify and resolve the root cause of the disruption to prevent a recurrence.
120
+ Finally, we conduct regular test restores to ensure that our backup system is working as intended. These tests verify the integrity of the backup data and the functionality of the restore process.
121
+ In summary, Argilla Cloud's comprehensive backup and recovery protocol, combined with our commitment to a short RPO and RTO, minimizes the risk of data loss and ensures swift recovery of your data in the event of any disruption.
122
+
123
+
124
+ Starter: Daily backups with a recovery point objective (RPO) of 24 hours and a recovery time objective (RTO) of 4 hours.
125
+ Base: Twice-daily backups with an RPO of 12 hours and an RTO of 2 hours.
126
+ Medium: 6 a-day backups with an RPO of 4 hours and an RTO of 1 hour.
127
+ Large: 6 a-day backups a, with an RPO of 4h hours and an RTO of 1 hour.
128
+
129
+ Prices available upon request
130
+
131
+ Details:
132
+ Monthly Plan: The monthly cost is billed at the beginning of each month. This plan offers flexibility as you can upgrade or downgrade your plan based on your usage and requirement.
133
+ Yearly Plan: The yearly cost is billed upfront at the beginning of the year. By choosing the yearly plan, clients benefit from a 10% discount compared to the total cost of the monthly plan over a year. This plan offers better value for clients with stable or predictable usage.
134
+