Different systems and how to get access
A list of systems related to CoFinder data processing and how to get access to them.
Use this page as the directory for ownership and access paths. If a system is missing, add it here rather than leaving the knowledge only in Slack.
General
| System | Link | What it does | Who can help you with access | Other comments? |
|---|---|---|---|---|
| GitHub org + CoFinder repo | linked | Required to clone the monorepo and contribute code | All developers in the project | You need access both to the GitHub organization and to the cofinder repository |
| SOPS secrets | linked | Most project secrets are stored in encrypted files in Git | All developers in the project | Secrets live in cofinder/secrets/*.env; developer keys live in cofinder/.sops.yaml |
| Age key / local secret decryption | Lets you decrypt the repo’s encrypted .env files locally |
All developers in the project | Typical setup is to generate an age key, get it added to .sops.yaml, then decrypt backend/.env, frontend/.env, and pipelines/.env |
|
Azure datadrivet-dev login |
linked | Microsoft login used during local development and some service integrations | Ask the team member onboarding you if this is missing | The current dev-container flow expects you to sign in and choose the datadrivet-dev tenant/account |
| Azure KeyVault | linked | A secure location to store some access information | Tom, Lunken, Jimmy, Ruben, Fredrik M | Ask to be added to team “Invativa” and to get role “Key Vault Secrets User” for datadrivet-cluster-prod |
| Keycloak | Identity provider for several internal platform services | Jimmy, Fredrik, Andreas, Jon-Erik, Ruben, Tomas | Linked to Vault, MinIO, and Onyxia | |
| Hashicorp Vault | linked | Stores secrets used by internal platform services | see Keycloak | Access typically follows your platform role |
Data
| System | Link | What it does | Who can help you with access | Other comments? |
|---|---|---|---|---|
| Snowflake web UI | linked | An easy way to look at the main database for the project | Jon-Erik, Fredrik, Andreas, Jimmy, Edvard | Your username will be of format cocreate<yourname>. You may need admin rights to create your copy of the database. |
| Snowflake API access | linked | Access main database for the project via code | Jon-Erik, Fredrik, Andreas, Jimmy, Edvard | The key pair setup is a bit convoluted, make sure you follow these instructions carefully |
| Dagster dashboard | linked | Web UI to inspect production pipeline runs and asset state | see Azure KeyVault | Username and password are in Azure datadrivet-cluster-prod secrets |
| MinIO | linked | S3-compatible object storage hosted by the platform team | see Keycloak | You should get access through Keycloak when you get added to Terraform as a developer |
| Onyxia | linked | Self-service portal for data services, code spaces, and other OSS tools | see Keycloak | Status changes over time; if unavailable, ask in Slack before assuming it is gone |
| DuckDB (local dev) | Repository-local | Default local dbt database in development | No separate access needed | Used locally for dev workflows; the path is configured via DUCKDB_PATH in the pipeline setup |
| LanceDB | Repository-local or service-local depending on workload | Vector store used for embedding-based retrieval | Ask the owning developer for the relevant service | Access is usually indirect through the pipeline or application rather than a shared UI; there is normally no shared UI to request access to |
LLM-related
| System | Link | What it does | Who can help you with access | Other comments? |
|---|---|---|---|---|
| Phoenix web UI | linked | Tracks LLM call traces and debugging metadata | see Azure KeyVault | API access info is in SOPS secrets |
| LiteLLM API definition | linked | API definition for the LiteLLM gateway | No login | |
| LiteLLM API keys | linked | API keys to access LiteLLM proxy either as an individual or as a project | Andreas, Jimmy, Jon-Erik | Jimmy can help with adding money |
| LiteLLM logs | linked | LiteLLM usage logs, costs, and API key management | Andreas, Jimmy, Jon-Erik | You likely do not need access unless you are tracking usage or costs |
| OpenRouter | linked | Site to inspect which models are available | No need to log in just to browse models | |
| Modal | linked | Site where CV-generator endpoint is hosted | Andreas | The modal workspace is limited to 3 people. Discuss with Andreas or Tomas if you think you need access. |