Oracle3
Oracle3: 예측시장 거래 엔진·MCP 서버
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Syllogic is an open-source personal finance app for self-hosters who want control over their data without giving up a polished product. Track balances, spending, recurring charges, and trends, import and export CSVs, and optionally enable AI categorization.
One-liner (requires root, Docker, and Docker Compose):
curl -fsSL https://github.com/syllogic-ai/syllogic/releases/latest/download/install.sh | sudo bash
Or manually:
Clone and configure:
Linux/macOS:
git clone https://github.com/syllogic-ai/syllogic.git
cd syllogic
cp deploy/compose/.env.example deploy/compose/.env
# Edit deploy/compose/.env — set POSTGRES_PASSWORD, BETTER_AUTH_SECRET, INTERNAL_AUTH_SECRET
Windows (PowerShell):
git clone https://github.com/syllogic-ai/syllogic.git
cd syllogic
copy deploy\compose\.env.example deploy\compose\.env
# Edit deploy\compose\.env — set POSTGRES_PASSWORD, BETTER_AUTH_SECRET, INTERNAL_AUTH_SECRET
Start:
Linux/macOS:
./scripts/prod-up.sh
Windows (PowerShell or CMD):
.\scripts\prod-up.bat
Open http://localhost:8080 and create your account.
For advanced configuration (TLS, custom domains, MCP server), see deploy/compose/README.md.
The template configures everything through Railway Shared Variables — one place
that every service reads from. The required secrets (POSTGRES_PASSWORD,
BETTER_AUTH_SECRET, INTERNAL_AUTH_SECRET, DATA_ENCRYPTION_KEY_CURRENT) are
auto-generated at deploy time, so a default deploy needs no manual input.
Optionally set these Shared Variables to enable extra features:
OPENAI_API_KEY (enables AI categorization)LOGO_DEV_API_KEY (enables company logos)For full Railway setup details, see deploy/railway/README.md.
Maintainers publishing the template: see deploy/railway/TEMPLATE.md.
For public demo environments, you can share a login URL that prefills demo credentials:
https://your-app-domain.com/login?demo=1
Syllogic public demo:
https://app.syllogic.ai/login?demo=1
Set these frontend environment variables on that deployment:
NEXT_PUBLIC_DEMO_EMAILNEXT_PUBLIC_DEMO_PASSWORDOptional auth throttling (recommended for public demos):
AUTH_RATE_LIMIT_ENABLED=trueAUTH_RATE_LIMIT_WINDOW_MS=60000AUTH_RATE_LIMIT_MAX_ATTEMPTS_PER_WINDOW=30DEMO_AUTH_RATE_LIMIT_MAX_ATTEMPTS_PER_WINDOW=10DEMO_AUTH_RATE_LIMIT_GLOBAL_MAX_ATTEMPTS_PER_WINDOW=120| Method | Use case | Docs |
|---|---|---|
| CasaOS | Home lab / NAS users | deploy/casaos/ |
The deployment configs in this repo — deploy/railway/, deploy/compose/,
deploy/casaos/ and the railway.*.toml files — describe how you can host
Syllogic. They are the supported, documented paths, and the one-click Railway
template is built from them.
They do not describe how app.syllogic.ai is
wired. That instance runs on Coolify on a single server,
and it is itself a self-hosted deployment of this same code — it just happens to
also serve the public demo login. Coolify is not listed above because it is not
packaged as a template here; if you want it, the deploy/compose/ stack is the
closest starting point.
One difference worth knowing if you are building a client against it: on that instance only the web app and the MCP endpoint are publicly reachable. The FastAPI service is private, and the web app proxies to it — so a mobile or third-party client authenticates against the web origin, not against the API directly. A self-hosted deployment can expose the API however it likes; nothing in the code requires this arrangement.
| Variable | Description | Required |
|---|---|---|
POSTGRES_PASSWORD | PostgreSQL password | Yes |
BETTER_AUTH_SECRET | Auth session signing key | Yes |
INTERNAL_AUTH_SECRET | App-to-backend signed auth | Yes |
DATA_ENCRYPTION_KEY_CURRENT | Field-level encryption key | Recommended |
OPENAI_API_KEY | AI transaction categorization | No |
LOGO_DEV_API_KEY | Company logo lookup | No |
Generate secrets with openssl rand -hex 32. For encryption keys: openssl rand -base64 32.
OPENAI_API_KEY — AI-powered categorization via OpenAI (GPT-4o-mini by default).
LOGO_DEV_API_KEY — Company logo lookup via logo.dev.
Full variable reference is available in deploy/compose/.env.example.
Both services share a single PostgreSQL database. The frontend handles all CRUD via Server Actions; the backend handles data enrichment, bank sync, and background jobs.
Syllogic models a household as a set of people belonging to one user. Accounts, properties, and vehicles can have one or more owners with optional shares (a NULL share means equal split). Holdings inherit ownership from their account. The Syllogic MCP read tools accept person_ids to scope results and attribute share-weighted amounts.
Track brokerage and crypto holdings with portfolio summaries and history. The Syllogic MCP exposes read tools for holdings, portfolio summary/history, and symbol search.
Quick start for contributors:
Everything runs in Docker using prebuilt images. Easiest setup for full-stack testing.
1. Clone and configure:
git clone https://github.com/syllogic-ai/syllogic.git
cd syllogic
cp deploy/compose/.env.example deploy/compose/.env
# Edit deploy/compose/.env — set INTERNAL_AUTH_SECRET, BETTER_AUTH_SECRET
# Keep DATABASE_URL=postgresql://...@postgres:5432/... (Docker internal)
2. Start the stack:
# Linux/macOS
./scripts/dev-up.sh --prebuilt
# Windows
.\scripts\dev-up.bat prebuilt
3. Open http://localhost:8080
Infrastructure runs in Docker, frontend runs on host. Best for frontend development with hot reload.
1. Clone and configure:
git clone https://github.com/syllogic-ai/syllogic.git
cd syllogic
cp deploy/compose/.env.example deploy/compose/.env
# Edit deploy/compose/.env — set INTERNAL_AUTH_SECRET, BETTER_AUTH_SECRET
2. Start infrastructure:
# Linux/macOS
./scripts/dev-up.sh --local
# Windows
.\scripts\dev-up.bat local
This starts PostgreSQL, Redis, and Celery workers, installs dependencies, runs migrations, and creates frontend/.env.local with the required environment variables.
3. Start the Next.js dev server:
cd frontend
pnpm dev
4. (Optional) Start the backend (required for CSV import and other backend features):
cd backend
uvicorn app.main:app --reload
5. Open http://localhost:3000
Note: Local mode runs only infrastructure. CSV import and other backend features require starting the backend (step 4) or using prebuilt mode.
See CONTRIBUTING.md for full setup instructions and code style guidelines.
Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).