About · Celiums Solutions, LLC

Built quietly.
Open by default.

Celiums is a small, focused company. A memory engine, an agent runtime, and specialized intelligences — assembled in the order each piece earned its place.

01 — The story

Memory came first.

The order matters. Memory was built first because nothing else worked without it. Models that forget every session can't be colleagues. They start cold. They miss the constraint you mentioned in passing. They contradict last quarter's decision because the decision left no trace.

Once memory existed, the agent that uses it followed naturally. Once the agent had a stable foundation, specialized intelligences became possible. Each piece earned its place by being needed, not by being planned.

We don't predict the network. We build the next part when it becomes the obvious part.
02 — Foundations

Standing on peer-reviewed work.

Memory isn't an opinion. It's a system grounded in how memory actually behaves in human cognition. The implementation cites its sources. Anyone can read them, test them, and disagree with them.

F01
PAD emotional model

Pleasure–Arousal–Dominance. Memories carry affective weight; recall ranks for resonance, not just semantic match.

Mehrabian & Russell, 1974
F02
Ebbinghaus forgetting

Retention decays. Importance is preserved through repeated activation. The forgetting curve is not a metaphor — it's the schedule.

Ebbinghaus, 1885
F03
Circadian context

When a memory was formed shapes how it surfaces. Time-of-day and rhythm signals are part of the recall index, not metadata.

Chronobiology of memory consolidation
F04
Open by default

The memory engine is Apache 2.0. Source on GitHub. SDK on npm. The work is auditable because it has to be.

Apache License 2.0 · open source in full
F05
Production stack

Managed Postgres, Valkey, OpenSearch, and Kubernetes — all on infrastructure you can replicate. No private deployment magic.

Postgres · Valkey · OpenSearch · K8s
F06
Born and raised on DigitalOcean

Every part of Celiums was built and shipped on DigitalOcean. Same droplets, same managed services, same regions you can spin up in minutes.

DigitalOcean · Droplets + Managed Services
03 — The maker

One person. For now.

Celiums is built by a solo founder. That's a choice, not an accident. Small surface area, clear decisions, no layers between the work and the person doing it.

Founder · Engineer
Mario Gutiérrez
Solo founder · self-taught engineer

Self-taught engineer working out of Medellín, Colombia. Originally from Venezuela. Building Celiums because the gap between what AI promises and what it remembers needed someone to close it — and the work is more interesting when grounded in published cognitive science instead of hype.

Open to collaboration once the foundation justifies it. Not before.

Based in Medellín · CO
Originally from Venezuela
04 — How we work

Principles, not slogans.

The way Celiums is built shapes what it becomes. These are not aspirations. They are the working rules.

P01
Ship over speak

If a piece isn't running in production, we don't claim it. Every capability on this site has a public surface you can verify.

P02
Open core

The engine is open. The user owns their memories and their agents. No telemetry, no extraction, no lock-in by design.

P03
Cite your work

Models grounded in peer-reviewed research, not vibes. Sources visible, claims testable, disagreement welcome.

P04
Earn the next step

Each new specialty waits until the depth of the field justifies the build. No premature breadth, no domains-by-the-dozen.

05 — Funding the work

Patronage, not investment.

Celiums is research. The engine, the journal, the ethics layer, the experiments — all of it is meant to stay open and auditable. That has implications for how we accept money.

We don't refuse sponsorship. We refuse sponsorship that would change what we are. The grid below makes the line explicit so no conversation starts on a misunderstanding.

What we welcome

Aligned with open research.

  • Research grants from universities, foundations, and government science programs. Standard publication terms.
  • Engineering sponsorship — cloud credits, GPU hours, managed infrastructure. Output remains under our licenses.
  • Individual sponsorships via GitHub Sponsors, recurring or one-time. Funds personal time; no governance attached.
  • Ecosystem partnerships with other open-source projects we already cite or depend on.
  • Roadmap-aligned commissionsfund a piece of work that was going to be built anyway, get acknowledgment in the journal.
What we decline

However big the cheque is.

  • Equity in exchange for direction. No venture capital. The roadmap is not for sale.
  • Exclusivity. No partner gets to be the only partner. Open means everyone keeps the right to fork.
  • Closed-source pivots. Any deal that requires hiding the engine, the journal, or the ethics layer is a deal we walk away from.
  • Data-extraction or telemetry deals. Users own their memories and their agents. We don't sell either, ever.
  • Defense, surveillance or other harm-shaped use cases. Even if it's legal where it ships. The acceptable-use policy is binding on us too.

How to propose sponsorship

One email. We respond honestly within a week — including when the answer is no. Tell us what you'd like to fund, what you'd like in return, and where you'd like the work documented.

  1. Who you are — organization, mission, why this work matters to you.
  2. What you propose — grant, credits, recurring sponsorship, roadmap commission.
  3. What you ask in return — acknowledgment, co-authorship, namespace, nothing.
  4. Where you stand on the grid above — your honest read of which side you fall on.
hello@celiums.ai
06 — Get in touch

Useful conversations only.

Direct technical questions, partnership conversations, journalists with substance — welcome. Anything else can wait.

hello@celiums.ai