chore: rebrand documentation to pica (#215)

Co-authored-by: Samuel Gomez <[email protected]>

Author: paulkr

README.md

@@ -1,29 +1,26 @@
 <p align="center">
-📖 Just launched <b><a href="https://www.integrationos.com/">IntegrationOS</a></b>
-  <br/>
- </p>
-
-<p align="center">
-  <a href="https://integrationos.com">
-    <img src="https://assets-global.website-files.com/5f6b97302bb70b93e591d51f/657a3a1aec47c8ec20b396fe_IntegrationOS%20main%20logo-p-500.png" height="64px">
+  <a href="https://picaos.com">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="./resources/images/logo-dark.svg">
+      <source media="(prefers-color-scheme: light)" srcset="./resources/images/logo-light.svg">
+      <img alt="Pica Logo" src="./resources/images/logo-light.svg" height="100px">
+    </picture>
   </a>
 </p>
 
-<p align="center"><b>Ship integrations, remarkably fast.</b></p>
+<p align="center"><b>The Complete Agentic Infrastructure</b></p>
 
 <p align="center">
   <b>
-    <a href="https://www.integrationos.com/">Website</a>
-    ·
-    <a href="https://docs.integrationos.com/docs/quickstart">Documentation</a>
+    <a href="https://www.picaos.com/">Website</a>
     ·
-    <a href="https://www.integrationos.com/changelog">Changelog</a>
+    <a href="https://docs.picaos.com">Documentation</a>
     ·
-    <a href="https://www.integrationos.com/blog">Blog</a>
+    <a href="https://www.picaos.com/community">Community Hub</a>
     ·
-    <a href="https://join.slack.com/t/integrationos-hq/shared_invite/zt-2dm9254tc-Eza~78acJllbP7ZFKuVYjw">Slack</a>
+    <a href="https://www.picaos.com/community/changelog">Changelog</a>
     ·
-    <a href="https://twitter.com/integrationos">Twitter</a>
+    <a href="https://twitter.com/picahq">Twitter</a>
   </b>
 </p>
 
@@ -38,39 +35,39 @@ Forget the pain of having to manually parse through, transform and maintain hund
 
 To get the most out of this guide, you'll need:
 
-1. An [IntegrationOS account](https://app.integrationos.com)
-2. Your  IntegrationOS [API Key](https://docs.integrationos.com/docs/glossary#api-key)
+1. A [Pica account](https://app.picaos.com)
+2. Your Pica [API Key](https://docs.picaos.com/docs/glossary#api-key)
 
 ## Step 1: Backend - Create secure tokens
 
 First, we'll add an endpoint to our backend that'll let us generate secure tokens for our frontend component.
 
 ### Install the SDK
 
-To make this easy, IntegrationOS offers native SDKs in several popular programming languages. This guide will use the popular AuthKit SDK for Node.js.
+To make this easy, Pica offers native SDKs in several popular programming languages. This guide will use the popular AuthKit SDK for Node.js.
 
 ```shell npm
-npm install @integrationos/authkit-node
+npm install @picahq/authkit-node
 ```
 
 ### Set secrets
 
-To make calls to IntegrationOS, provide your API key. Store these values as managed secrets and pass them to the SDKs either as environment variables or directly in your app's configuration depending on your preferences.
+To make calls to Pica, provide your API key. Store these values as managed secrets and pass them to the SDKs either as environment variables or directly in your app's configuration depending on your preferences.
 
 ```shell
-INTEGRATIONOS_SANDBOX_API_KEY='sk_test_example_123456789'
-INTEGRATIONOS_PRODUCTION_API_KEY='sk_live_example_123456789'
+PICA_SANDBOX_API_KEY='sk_test_example_123456789'
+PICA_PRODUCTION_API_KEY='sk_live_example_123456789'
 ```
 
 ### Create a token endpoint
 
 Next, we'll need to add the token endpoint which will exchange the authorization token (valid for 10 minutes) for an authenticated Connected Account.
 
 ```javascript
-import { AuthKitToken } from "@integrationos/authkit-node";
+import { AuthKitToken } from "@picahq/authkit-node";
 
 app.post("/authkit-token", async (request, response) => {
-  const authKitToken = new AuthKitToken(process.env.INTEGRATIONOS_SANDBOX_API_KEY);
+  const authKitToken = new AuthKitToken(process.env.PICA_SANDBOX_API_KEY);
 
   // Specifying how the token will be constructed
   const token = await authKitToken.create({
@@ -89,18 +86,18 @@ Next, we'll add the AuthKit component to your frontend application.
 
 ### Install the SDK
 
-In the same fashion, IntegrationOS offers native frontend SDKs in several popular frameworks. Compatible with React, Next.js, Vue, Svelte and more.
+In the same fashion, Pica offers native frontend SDKs in several popular frameworks. Compatible with React, Next.js, Vue, Svelte and more.
 
 ```shell npm
-npm install @integrationos/authkit
+npm install @picahq/authkit
 ```
 
 ### Use the AuthKit Component
 
 Next, we need to add the AuthKit component and replace the token URL with the URL of the token endpoint URL you created in Step 1 of this guide.
 
 ```javascript
-import { useAuthKit } from "@integrationos/authkit";
+import { useAuthKit } from "@picahq/authkit";
 
 const { open } = useAuthKit({
   token: {
@@ -129,15 +126,13 @@ This will open the AuthKit modal so your user can:
 
 Once the flow is completed, AuthKit will return a Connection object to your onSuccess callback. Each connection object contains metadata about the connected account and can be used to make API requests.
 
-View the full guide [here](https://docs.integrationos.com/docs/quickstart).
+View the full guide [here](https://docs.picaos.com).
 
-# Running IntegrationOS locally
+# Running Pica locally
 
 ## Prerequisites
 
 * [Docker](https://docs.docker.com/engine/) and [Docker Compose](https://docs.docker.com/compose/)
-* A [Google Cloud KMS](https://cloud.google.com/kms/docs) key ring
-* [`gcloud`](https://cloud.google.com/sdk/gcloud) installed, logged into an account that has `roles/cloudkms.cryptoKeyEncrypterDecrypter` access, and configured with [Application Default Credentials](https://cloud.google.com/docs/authentication/provide-credentials-adc)
 
 ## Setup
 
@@ -156,18 +151,18 @@ View the full guide [here](https://docs.integrationos.com/docs/quickstart).
     docker compose -f docker-compose.data.yml run --rm seed-data
     ```
 
-**Note:** If you want to run the latest version of the docker image, you can use the latest git commit hash as the tag. For example, `integrationos/integrationos:<commit-hash>`.
+**Note:** If you want to run the latest version of the docker image, you can use the latest git commit hash as the tag. For example, `picahq/pica:<commit-hash>`.
 
 ## Other actions
 
 Connecting to a MongoDB shell
 
 ```shell
 source .env
-docker compose exec mongo mongosh -u integrationos -p $MONGO_PASSWORD --authenticationDatabase=admin events-service
+docker compose exec mongo mongosh -u pica -p $MONGO_PASSWORD --authenticationDatabase=admin events-service
 ```
 
 
 # License
 
-IntegrationOS is released under the [**GPL-3.0 license**](LICENSE).
+Pica is released under the [**GPL-3.0 license**](LICENSE).

docker-compose.yml

@@ -1,7 +1,7 @@
 services:
   typescript-services:
     platform: linux/amd64
-    image: us-docker.pkg.dev/integrationos/docker-oss/typescript-services:1.24.0
+    image: us-docker.pkg.dev/pica/docker-oss/typescript-services:1.24.0
     ports:
       - 3001:3001
     environment:
@@ -27,7 +27,7 @@ services:
 
   connections-api:
     platform: linux/amd64
-    image: us-docker.pkg.dev/integrationos/docker-oss/api:1.24.0
+    image: us-docker.pkg.dev/pica/docker-oss/api:1.24.0
     ports:
       - 3005:3005
     environment:
@@ -57,7 +57,7 @@ services:
 
   event-core:
     platform: linux/amd64
-    image: us-docker.pkg.dev/integrationos/docker-oss/event-core:1.24.0
+    image: us-docker.pkg.dev/pica/docker-oss/event-core:1.24.0
     environment:
       - CONTEXT_COLLECTION_NAME=event-transactions
       - CONTEXT_DATABASE_NAME=events-service
@@ -80,7 +80,7 @@ services:
 
   gateway:
     platform: linux/amd64
-    image: us-docker.pkg.dev/integrationos/docker-oss/gateway:1.24.0
+    image: us-docker.pkg.dev/pica/docker-oss/gateway:1.24.0
     ports:
       - 3002:3002
     environment:
@@ -98,7 +98,7 @@ services:
 
   oauth-refresh:
     platform: linux/amd64
-    image: us-docker.pkg.dev/integrationos/docker-oss/oauth-refresh:1.24.0
+    image: us-docker.pkg.dev/pica/docker-oss/oauth-refresh:1.24.0
     ports:
       - 3003:3003
     environment:
@@ -124,7 +124,7 @@ services:
 
   watchdog:
     platform: linux/amd64
-    image: us-docker.pkg.dev/integrationos/docker-oss/watchdog:1.24.0
+    image: us-docker.pkg.dev/pica/docker-oss/watchdog:1.24.0
     environment:
       - CONTEXT_COLLECTION_NAME=event-transactions
       - CONTEXT_DATABASE_NAME=events-service

integrationos-api/README.md

@@ -1,6 +1,6 @@
-## IntegrationOS API
+## Pica API
 
-Common API for the IntegrationOS project.
+Common API for the Pica project.
 
 For a full list of endpoints, please refer to the following files:
 

integrationos-archiver/README.md

@@ -1,10 +1,10 @@
-# IntegrationOS Archiver
+# Pica Archiver
 
-A Rust-based archiver for the IntegrationOS project that archives the specified database.
+A Rust-based archiver for the Pica project that archives the specified database.
 
 ## Purpose
 
-IntegrationOS Archiver is a service designed to archive data from a specified database efficiently. It is built using Rust to ensure high performance and reliability in handling large volumes of data.
+Pica Archiver is a service designed to archive data from a specified database efficiently. It is built using Rust to ensure high performance and reliability in handling large volumes of data.
 
 ## Running the Archiver
 

integrationos-cache/README.md

@@ -1,10 +1,10 @@
-# IntegrationOS Cache
+# Pica Cache
 
-A minimal wrapper around Moka and Redis for caching in the IntegrationOS project.
+A minimal wrapper around Moka and Redis for caching in the Pica project.
 
 ## Purpose
 
-IntegrationOS Cache provides a lightweight, minimalistic interface to manage caching operations using Moka and Redis. While it is not runnable as a standalone service, it can be integrated into other systems and thoroughly tested to ensure reliable caching behavior.
+Pica Cache provides a lightweight, minimalistic interface to manage caching operations using Moka and Redis. While it is not runnable as a standalone service, it can be integrated into other systems and thoroughly tested to ensure reliable caching behavior.
 
 ## Running the Tests
 

integrationos-database/README.md

@@ -1,10 +1,10 @@
-# IntegrationOS Storage
+# Pica Storage
 
-A versatile wrapper around multiple storage solutions, designed for single-tenant management of clients in the IntegrationOS project.
+A versatile wrapper around multiple storage solutions, designed for single-tenant management of clients in the Pica project.
 
 ## Purpose
 
-IntegrationOS Storage provides a unified interface for managing different storage backends, enabling single-tenant configurations for clients. It supports seamless integration of new databases, making it adaptable to various storage needs.
+Pica Storage provides a unified interface for managing different storage backends, enabling single-tenant configurations for clients. It supports seamless integration of new databases, making it adaptable to various storage needs.
 
 ## Running the Storage Service
 

integrationos-domain/README.md

@@ -1,11 +1,11 @@
-# IntegrationOS Domain
+# Pica Domain
 
 This documentation does not aim to be an in-depth explanation of the code, but rather a high-level overview of the project.
 For a more detailed explanation, please refer to the code itself.
 
 ## Overview
 
-IntegrationOS domain seeks to hold the common data structures used on the [integration-os](https://github.com/integration-os/integration-os) repository. Along with these DS, it also
+Pica domain seeks to hold the common data structures used on the [pica](https://github.com/picahq/pica) repository. Along with these DS, it also
 has some utilities to create `id` and manipulate `json` as well as general purpose services.
 
 ### Environment Variables
@@ -40,14 +40,14 @@ The following environment variables are introduced, not necessarily used, by thi
 
 ### Services
 
-- Caller Client: A client to make requests to external APIs. It is used to make requests to external APIs and return the response. It is used by the `integration-os` repository to make requests to external APIs.
-- Secrets Client: A client to interact with the secrets service. It is used to get and create secrets in the secrets service. It is used by the `integration-os` repository to get and create secrets.
-- Watchdog Client: A client to start and stop the watchdog service. It is used to start the watchdog service. It is used by the `integration-os` repository to start and stop the watchdog service.
+- Caller Client: A client to make requests to external APIs. It is used to make requests to external APIs and return the response. It is used by the `pica` repository to make requests to external APIs.
+- Secrets Client: A client to interact with the secrets service. It is used to get and create secrets in the secrets service. It is used by the `pica` repository to get and create secrets.
+- Watchdog Client: A client to start and stop the watchdog service. It is used to start the watchdog service. It is used by the `pica` repository to start and stop the watchdog service.
 
 ### Data Structures
 
 Please refer to the code itself for a detailed explanation of the data structures.
 
 ### Utilities
 
-- Hash Data: A utility to hash data. It is used to hash data and return the hash. It is used by the `integration-os` repository to hash data.
+- Hash Data: A utility to hash data. It is used to hash data and return the hash. It is used by the `pica` repository to hash data.

integrationos-event/README.md

@@ -1,4 +1,4 @@
-# IntegrationOS Event
+# Pica Event
 
 Processes incoming events from the [gateway](../integrationos-gateway/) over redis and executes the associated pipelines.
 

integrationos-gateway/README.md

@@ -1,10 +1,10 @@
-# IntegrationOS Gateway
+# Pica Gateway
 
 Receives events by POSTing to the `/emit/:access_key` endpoint. Validates the access key and then stores the event in mongodb and transmits it over redis.
 
 ## Dependencies
 
-Requires redis to send events to the [integrationos-event](../integrationos-event) service.
+Requires redis to send events to the [pica-event](../integrationos-event) service.
 
 ```bash
 $ docker run -p 6379:6379 redis

integrationos-oauth/README.md

@@ -1,4 +1,4 @@
-# IntegrationOS OAuth API
+# Pica OAuth API
 
 The API for OAuth based Connections.
 

integrationos-oauth/package.json

@@ -39,4 +39,4 @@
     "eslint-plugin-prettier": "^4.2.1",
     "prettier": "^2.7.1"
   }
-}
+}

integrationos-unified/README.md

@@ -1,12 +1,12 @@
-# IntegrationOS Unified
+# Pica Unified
 
-The core logic for unification APIs and user request handling in the IntegrationOS project.
+The core logic for unification APIs and user request handling in the Pica project.
 
 ## Purpose
 
-IntegrationOS Unified provides the core functionality for managing and processing unification APIs, ensuring proper handling of user requests across the IntegrationOS ecosystem. While this service is not directly runnable, its logic forms the backbone of the unification process within the system.
+Pica Unified provides the core functionality for managing and processing unification APIs, ensuring proper handling of user requests across the Pica ecosystem. While this service is not directly runnable, its logic forms the backbone of the unification process within the system.
 
-For detailed usage and API references, visit the [API documentation](https://docs.integrationos.com/reference/list-connections).
+For detailed usage and API references, visit the [API documentation](https://docs.picaos.com).
 
 ## Running the Tests