Teams & Projects¶
TL;DR — 8 teams at Securitize (ON, ISR, TA, BC, JP, BlackOps, DevOps, SEC), their Bitbucket projects, Jira projects, and contacts. Also documents the non-team-owned
SHARBitbucket project and theCTDCross Tech Debt Jira board. This page is the single source of truth for team ownership — every other page links here, none duplicate.
Overview¶
Securitize has 4 feature teams (ON, ISR, TA, BC) + 1 regional team (JP, Japan-region products) + DevOps + BlackOps (architecture / cross-cutting) + 1 security team (SEC). Each team owns specific Bitbucket projects and uses a dedicated Jira project for its work.
In addition, a SHAR Bitbucket project and a CTD Jira board exist but are not owned by any specific team — see the Non-team-owned projects section below.
Teams and project mapping¶
| Team | Responsibility | Bitbucket Projects | Jira Project |
|---|---|---|---|
| Onboarding Team (ON) | Investor-facing experience, onboarding, KYC, Cash Account, Fundraise, Securitize ID | CA, ATS, FR, II, SID | ON |
| ISR (Issuer Experience) | Control Panel for issuers (configure tokens, deploy new tokens, etc.) | ISR | ISR2 |
| TA (Transfer Agent) | Transfer Agent functionality | TA | TA |
| BC (Blockchain) | Smart Contracts, blockchain abstraction layer microservices | BC | BC |
| JP (Japan) | Japan-region products | JP | JPD |
| BlackOps | Architecture & cross-cutting operational concerns | AO | AO |
| DevOps | Infrastructure, CI/CD, deployments | OPS | OPS |
| SEC (Security) | Security & compliance | SEC | SEC |
Non-team-owned projects¶
Some Bitbucket projects and Jira boards are not owned by a specific team:
| Project / Board | What it is | Notes |
|---|---|---|
SHAR (Bitbucket project) |
Hosts shared libraries used across teams — see Shared Libraries (nestjs-shared, reactjs-shared, commons-shared). |
Not owned by any team. Cross-team contributions. |
CTD (Jira board, "Cross Tech Debt") |
Tracks cross-team initiatives: architecture work, standardization, tech debt. | Not owned by any team. |
Contacts¶
Technical references and team leaders per team, with Slack ID and email for quick outreach.
| Team | Role | Name | Slack ID | |
|---|---|---|---|---|
| Onboarding Team (ON) | Team Leader | Gabriel Fresco | U0167TY8FB4 |
gabriel.fresco@securitize.io |
| Onboarding Team (ON) | Technical Reference | Leonardo D'Antoni | U040WF06S78 |
leonardo.d.antoni@securitize.io |
| Onboarding Team (ON) | Technical Reference | Guillermo Freschi | U02LF2YD6GG |
guillermo.freschi@securitize.io |
| ISR (Issuer Experience) | Team Leader | Luciano Conde | U015D96CRFV |
luciano@securitize.io |
| ISR (Issuer Experience) | Technical Reference | Leandro Briglio | U052VT2GRC1 |
leandro.briglio@securitize.io |
| TA (Transfer Agent) | Team Leader | Matias L. Sanchez | U018ZGP7ZB6 |
matias.sanchez@securitize.io |
| TA (Transfer Agent) | Technical Reference | Nicolas Goldberg | U02L81N3FL6 |
nicolas.goldberg@securitize.io |
| BC (Blockchain) | Team Leader | David Ezequiel Assen | U017F6K77PA |
david.assen@securitize.io |
| BC (Blockchain) | Technical Reference | Joaquín Larrañaga | U02UDB5P23V |
joaquin.larranaga@securitize.io |
| JP (Japan) | Team Leader | Daisuke | URGBJ8CUX |
daisuke@securitize.io |
| BlackOps | Team Leader | Gil Hadad | U02S7A0EJ9W |
gil.hadad@securitize.io |
| BlackOps | Technical Reference | Alex K | U9QLC87DG |
alex@securitize.io |
| DevOps | Team Leader | DrorM | UJPK54HB4 |
dror@securitize.io |
| DevOps | ARG Engineer | Leandro Vidal | U091EGJ5JLU |
leandro.vidal@securitize.io |
| DevOps | ARG Engineer | Gonzalo Correa | U05B6SERQ4Q |
gonzalo.correa@securitize.io |
| DevOps | ARG Engineer | Nicolas Marque | U05C0DADVDK |
nicolas.marque@securitize.io |
| SEC (Security) | Team Leader | David Yerushalmi | URLJL6WSE |
david@securitize.io |
Repos and source control¶
- Bitbucket (
securitize_devworkspace) — ~150 repos. Everything except Smart Contracts. - GitHub — Smart Contracts only (owned by the BC team).
For the detailed catalog of ops-* repos, see ops-repos.md.
For the full catalog of Bitbucket repos, see the Repository References Confluence page.
Code ownership¶
There is no formal CODEOWNERS file per repo. Ownership is inferred by the Bitbucket project the repo lives in — the column "Bitbucket Projects" above is the source of truth. For review rules, see code-reviews.md.
See also¶
- Jira Boards — Board URLs per team (URLs only, mapping stays here).
- Ops Repositories — Detailed catalog of ops-* repos (owned by the DevOps team).
- Code Reviews — Review policy and ownership implications.