a management tool for companies
  • Rust 93.2%
  • Shell 5.7%
  • CSS 0.7%
  • Makefile 0.4%
Find a file
despiegk a3cfa2c4e8
Some checks failed
lab publish / publish (push) Failing after 52s
chore: remove all hard version pinning from hero_* dependencies
2026-06-06 08:41:30 +02:00
.cargo chore: add local development config and update hero_zero_sdk dependency 2026-01-30 21:13:07 -05:00
.claude refactor: Make Store methods async for Hero0 integration 2026-01-21 15:40:16 +01:00
.forgejo/workflows ci: build with lab, publish rolling latest/dev musl releases 2026-06-02 16:31:30 +02:00
_archive chore: rename FORGEJO_TOKEN→FORGE_TOKEN in CI; normalize heroscript indentation and PATH_SOCKET refs 2026-05-26 12:26:46 +02:00
crates chore: remove all hard version pinning from hero_* dependencies 2026-06-06 08:41:30 +02:00
instructions chore: rename FORGEJO_TOKEN→FORGE_TOKEN in CI; normalize heroscript indentation and PATH_SOCKET refs 2026-05-26 12:26:46 +02:00
scripts chore: rename FORGEJO_TOKEN→FORGE_TOKEN in CI; normalize heroscript indentation and PATH_SOCKET refs 2026-05-26 12:26:46 +02:00
.gitignore chore: add .hero/ to .gitignore 2026-05-12 17:00:00 +02:00
buildenv.sh fix(hero_biz_admin): Rust 2024 closure types, clippy, and CI build scripts 2026-05-08 12:24:42 +02:00
Cargo.toml chore: remove all hard version pinning from hero_* dependencies 2026-06-06 08:41:30 +02:00
Cargo.toml.hero_builder_backup refactor(hero_biz): migrate from hero_service/hero_proc_sdk to hero_lifecycle 2026-05-29 20:20:39 +02:00
Makefile refactor: rename hero_biz_ui -> hero_biz_admin (ui.sock -> admin.sock) (#46) 2026-05-08 02:05:57 +00:00
PURPOSE.md chore: rename FORGEJO_TOKEN→FORGE_TOKEN in CI; normalize heroscript indentation and PATH_SOCKET refs 2026-05-26 12:26:46 +02:00
README.md chore: rename FORGEJO_TOKEN→FORGE_TOKEN in CI; normalize heroscript indentation and PATH_SOCKET refs 2026-05-26 12:26:46 +02:00
rust-toolchain.toml chore(toolchain): align rust-toolchain.toml to 1.96 and Cargo.toml rust-version to 1.95.0 2026-06-01 07:11:54 +02:00

HeroBiz

A web frontend for venture fund management, powered by HeroOsis backend.

Overview

HeroBiz is a client application that provides a web UI for managing business entities. It does not include its own database - all data is stored and managed by a HeroOsis server.

Managed Entities

  • Persons - Team members, investors, contacts
  • Companies - Portfolio companies, partners, vendors
  • Contracts - Agreements, terms, legal documents
  • Contacts - Communication records and interactions
  • Opportunities - Pipeline and deal flow
  • Deals - Investment transactions
  • Instruments - Financial instruments (SAFE, equity, etc.)
  • Transactions - Financial transactions and payments
  • Projects - Project management with milestones and tasks

Prerequisites

HeroOsis Server

HeroBiz requires a running HeroOsis server. HeroOsis must be started separately before running HeroBiz.

service osis start

Seeding HeroOsis with Initial Data

HeroOsis supports auto-seeding the database from TOML files on startup.

TOML File Format

Each TOML file should include a _type field:

_type = "Company"
name = "ACME Corporation"
description = "A technology company"
types = ["tech"]
tags = ["portfolio"]
active = true

If _type is not specified, the type is inferred from:

  1. The parent directory name (if it's not the domain directory)
  2. The filename prefix (e.g., company_acme.tomlCompany)

Configuration

Environment Variable Default Description
HERO_OSIS_URL http://localhost:9988 HeroOsis server API endpoint
HERO_OSIS_CONTEXT default HeroOsis context name

Running

# Start (builds and registers with hero_proc)
service biz start --update

# Start fresh (reset sockets + state)
service biz start --update --reset

# Stop
service biz stop

# Check status
service biz status

Open the admin UI via hero_router at /hero_biz/admin in your browser.

Architecture

Browser → hero_router → hero_biz_admin (admin.sock) → hero_osis (via hero_osis_sdk)
 → hero_biz (rpc.sock)

Sockets (Hero Sockets architecture)

Binary Socket ($PATH_SOCKET/hero_biz/)
hero_biz rpc.sock
hero_biz_admin admin.sock

Testing

HeroBiz includes end-to-end tests that verify the HeroOsis SDK integration.

# Run all tests (server-dependent tests will be skipped if HeroOsis is not running)
cargo test

# Run E2E tests with verbose output
cargo test --test e2e_hero_osis -- --nocapture

For full E2E testing, start HeroOsis first:

service osis start

Set HERO_OSIS_URL to test against a different server:

HERO_OSIS_URL=http://192.168.1.100:9080 cargo test --test e2e_hero_osis -- --nocapture