I build the whole platform, from schema to server. Database design, application code, deployment and monitoring are all mine. Every figure on this page is a measured result. The method sits next to it.
The three badges above are live. A monitor on my own server probes each upstream every two minutes and answers on a public endpoint. When a service goes down the badge turns grey while I am still asleep.
A social platform built on a point economy. Members earn, spend and transfer points. Clubs, leaderboards and live rooms run on that ledger. Every balance change is an append-only entry, so a balance is never silently overwritten.
| Database tables | Endpoints | Subdomains | Status |
|---|---|---|---|
| 60 | 402 | 6 | In development |
An astrology calculation engine that runs on its own core. I wrote the C kernel that reads NASA JPL's 623 MB DE422 ephemeris file. There is no third party ephemeris library in the stack, no AGPL exposure, and birth data stays on the server.
| Lines of C | Celestial bodies | RMS vs NASA JPL | Full natal chart |
|---|---|---|---|
| ~18,900 | 1308 | 0.11″ to 0.19″ | 0.12 ms |
Accuracy: audited against NASA JPL Horizons, 1900 to 2100
Ecliptic longitude measured against JPL Horizons apparent values at quarterly steps across two centuries. The query definition and the raw CSV are published.
| Body | RMS | 95th pct | Max |
|---|---|---|---|
| Sun | 0.11″ | 0.20″ | 0.24″ |
| Moon | 0.11″ | 0.20″ | 0.24″ |
| Mercury | 0.11″ | 0.20″ | 0.25″ |
| Venus | 0.11″ | 0.20″ | 0.24″ |
| Mars | 0.11″ | 0.20″ | 0.24″ |
| Jupiter | 0.19″ | 0.21″ | 3.52″ |
| Saturn | 0.11″ | 0.21″ | 0.28″ |
| Uranus | 0.12″ | 0.22″ | 0.26″ |
| Neptune | 0.12″ | 0.22″ | 0.24″ |
| Pluto | 0.19″ | 0.38″ | 0.44″ |
Jupiter carries one isolated 3.5″ deviation near 1949. Neighbouring dates are clean and the raw data parses correctly. I did not identify its source in this audit, so it stays in the table.
ΔT uses the standard IERS and Stephenson-Morrison-Hohenkerk model. Output agrees with Skyfield to within 0.0003″ on the same DE kernel. That figure confirms the engine applies IAU 2000A/2006 conventions correctly, and it is an internal consistency check.
Speed: measured under a cold moment discipline
| Measurement | Result |
|---|---|
| Single body, cold moment | 51 µs |
| Per body inside a chart | 5.5 µs |
| Throughput inside chart computation | ~180,000 bodies/s |
| Full natal chart (ephemeris + houses) | 0.12 ms |
Every call uses a different instant, scattered across 1960 to 2020. A repeated moment returns from cache at 0.7 µs, so those calls are excluded. Single body over 30,000+ calls. Charts over 4,000 people, median of three runs, warmup dropped. Reference server, single core.
Two findings from the audit work
The Moon under Lilith. Interpolated Lilith marks the direction of the Moon's orbital apogee, so it is only as sound as the Moon beneath it. This engine takes the Moon from the numerically integrated DE422. Most astrology software still leans on an analytic lunar series from 1991. Measured against JPL Horizons across 1955 to 2024, lunar longitude here departs by 0.11″ and that analytic series by 0.57″. Five times closer to NASA. Lilith inherits the advantage, and the few arcsecond gap against other tools is deliberate.
A comet in the wrong sign. Validating hyperbolic and long period orbits against Horizons surfaced a ~30° error in a widely used reference implementation's Hale-Bopp position. A full zodiac sign off.
astromansion.com · API docs · Swagger
My company. We build AI-integrated web software for businesses, and we operate what we ship.
Systems under load. Atomic database operations, row locks, append-only ledgers, idempotency keys. Running the same job twice has no additional effect.
Real-time infrastructure. WebSocket connections and a mediasoup SFU. Each worker holds its own RTC port range, and resources are released when a room empties.
Numerical computation. A C library that reads JPL ephemeris files, with its own Kepler solver for elliptic and hyperbolic orbits. Output verified against NASA JPL Horizons.
Infrastructure. Nginx, systemd, Cloudflare, PostgreSQL, Redis, Celery, Prometheus. I install them and I operate them.
Slow site, unstable server, messy data, or no idea where to start. Tell me what the system needs to do and I will tell you what it takes.
founder@mustafayavuzak.com · mustafayavuzak.com · x · linkedin
I am Unbound.