AI Engineering Platform
Infrastructure and tooling for AI Engineering bootcamps, providing secure, isolated development environments and automated participant onboarding.
Overview
This platform consists of the following components:
- Coder Deployment - Containerized development environments supported by Coder
- Participant Onboarding System - Secure, automated participant onboarding
1. Coder Deployment for GCP
The coder folder contains all resources needed to deploy a Coder instance on Google Cloud Platform (GCP), along with reusable workspace templates and Docker images for the workspace environment.
Structure
- deploy/ - Terraform scripts and startup automation for provisioning the Coder server on a GCP VM
- docker/ - Dockerfiles and guides for building custom images used by Coder workspace templates
- templates/ - Coder workspace templates for reproducible, containerized development environments on GCP
Usage
- Provision Coder on GCP - Follow the steps in
coder/deploy/README.md - Build and Push Docker Images - See
coder/docker/README.md - Push Workspace Templates - See
coder/templates/README.md
2. Participant Onboarding System
Automated API key distribution for bootcamp participants using GCP Secret Manager and workload identity.
- Secrets never written to disk — exported into the shell via
eval "$(onboard ...)" - Workspace VMs authenticate directly to Secret Manager via workload identity (no Firebase, no token service)
- Per-participant JSON secrets named
{bootcamp-name}-env-{github-handle} - Firestore tracks participant records and onboarded status
Architecture
Admin Phase
1. Setup participants/teams in Firestore
2. Generate API keys (Gemini, Langfuse, etc.)
3. onboard admin setup-secrets → creates per-participant Secret Manager secrets
4. Grant workspace SA roles/secretmanager.secretAccessor
5. Add users to GitHub org
Participant Phase
1. eval "$(onboard --bootcamp-name <name>)" in Coder workspace
2. Fetches env vars from Secret Manager via workload identity
3. Runs integration tests (env vars injected, nothing written to disk)
4. Marks participant as onboarded in Firestore
1 maintainer
Metadata
1 maintainer
Release files for aieng-platform-onboard 0.7.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aieng_platform_onboard-0.7.5.tar.gz | 41.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aieng_platform_onboard-0.7.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 93.2 kB
Release files / aieng_platform_onboard-0.7.5.tar.gz
| Download URL | aieng_platform_onboard-0.7.5.tar.gz |
|---|---|
| Size | 41.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8599442c2ef6a797cd91b4354c64e862d1efa665fbf56280199849520bb7ddc2
|
|
BLAKE2b-256 checksum How to use checksums |
841104b1dc271700b6deb381f11c42b6b4ac5fa1a89d2a27a33a2e4aa5aef330
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logRelease files / aieng_platform_onboard-0.7.5-py3-none-any.whl
| Download URL | aieng_platform_onboard-0.7.5-py3-none-any.whl |
|---|---|
| Size | 51.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b79a6a4e0f4a76c555ede2bdf23f0041fbe27447f9d52ce75bb5e9dddae0ac6
|
|
BLAKE2b-256 checksum How to use checksums |
e60febc59e4e7ff0f9d9bf7299029acddf3daecd15df7f8ef64e17f0e97ea64b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logSecurity for aieng-platform-onboard 0.7.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aieng_platform_onboard-0.7.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
