Trajectory Platform
Import your data, convert them into Trajectories, and receive endpoints via the Trajectory Platform.
Currently supports Langsmith Integration (Braintrust coming soon).
All processing happens on your machine and your API key never leaves your environment.
Prerequisites
- Python 3.11+
- UV (Python package manager)
- Node.js (v18+)
- A LangSmith API key (
lsv2_pt_...)
Quick Start
./run.sh
This single command handles everything:
- Creates a Python virtual environment (via
uv venv) if one doesn't exist - Installs backend dependencies
- Installs frontend dependencies (if
node_modulesis missing) - Starts the FastAPI backend on http://localhost:8000
- Starts the Vite dev server on http://localhost:5173
Open http://localhost:5173 in your browser, enter your LangSmith API key, and start browsing traces.
Press Ctrl+C to stop both servers.
Manual Setup
If you prefer to run things separately:
Backend
uv venv
uv pip install -r server/requirements.txt
uv run uvicorn server.main:app --reload
The API server will be available at http://localhost:8000.
Frontend
cd frontend
npm install
npm run dev
The frontend dev server will be available at http://localhost:5173. It proxies /api requests to the backend automatically.
Project Structure
.
├── server/ # FastAPI backend
│ ├── main.py # App setup, CORS, routes
│ ├── routers/ # API endpoint definitions
│ │ ├── projects.py # Project listing & validation
│ │ └── threads.py # Thread/conversation endpoints
│ ├── services/
│ │ └── langsmith.py # LangSmith API interaction
│ └── models/
│ └── schemas.py # Pydantic request/response models
├── frontend/ # React + TypeScript frontend
│ ├── src/
│ │ ├── components/ # UI components
│ │ ├── context/ # React context (auth state)
│ │ ├── api/ # API client
│ │ └── types/ # TypeScript type definitions
│ └── vite.config.ts # Vite config with API proxy
├── run.sh # Development startup script
└── pyproject.toml # Python project config
Available Scripts
| Command | Description |
|---|---|
./run.sh |
Start both backend and frontend |
npm run dev |
Start frontend dev server only (from frontend/) |
npm run build |
Type-check and build frontend for production |
npm run lint |
Run ESLint on frontend code |
npm run preview |
Preview production build |
License
Metadata
Release files for trajectory-server 0.1.0
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 | Actions |
|---|---|---|---|---|
| trajectory_server-0.1.0.tar.gz | 13.6 kB | Without provenance | Details for trajectory_server-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| trajectory_server-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for trajectory_server-0.1.0-py3-none-any.whl |
Total release size: 27.7 kB
Release files / trajectory_server-0.1.0.tar.gz
| Download URL | trajectory_server-0.1.0.tar.gz |
|---|---|
| Size | 13.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
406e24feb8cd4fb510bf37457652f4ee5436aa138593ee317f2d9774a45b2bb3
|
|
BLAKE2b-256 checksum How to use checksums |
3f66d1f058b4f6834e4e5325162410d16844a4c11d25fdf60aeb832c6f1e919f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / trajectory_server-0.1.0-py3-none-any.whl
| Download URL | trajectory_server-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8e6ceeb1cab55d905032f49e0698b074162fa9eba9be1ba79011d41b0a7e9b9
|
|
BLAKE2b-256 checksum How to use checksums |
c383a3dca201df2b48b8e1c1a6c79287865819dee8279427b9970bfe5d021bf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for trajectory-server 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.