Licensing question: using Graphiti from a proprietary system via HTTP sidecar

[qengine13]

Hi — we're evaluating Graphiti as a
knowledge graph layer in a proprietary financial system.

Architecture: Our system communicates with Graphiti exclusively via HTTP. No shared
process, no shared memory, no code inclusion. Graphiti runs as an independent sidecar
service.

Question: Under Apache-2.0, does this usage pattern create any obligation to
open-source our proprietary system? We want to confirm the HTTP boundary is a clean
separation under the license terms.

We're aware Apache-2.0 has no network copyleft (unlike AGPL-3.0), so we believe the answer
is no — but wanted to confirm directly with maintainers before committing to the
integration.

Thanks.

[akkupratap323]

From a licensing standpoint, using Graphiti as an HTTP sidecar where your proprietary financial system only talks to it over HTTP with no shared process shared memory or direct code linkage does not require you to open source your proprietary system under the Apache 2.0 license.

Apache 2.0 is a permissive license and does not impose network use copyleft unlike AGPL 3.0. As long as your system just calls Graphiti through its HTTP API and does not statically or dynamically link Graphiti’s code into your own binaries your proprietary code stays outside the scope of the license.

You still need to keep Graphiti’s license and copyright notices intact and if you actually modify Graphiti itself rather than just calling it as a service those changes must follow Apache 2.0 if you distribute them. But in an HTTP sidecar setup like this the separation is generally treated as clean and safe under the license.