Frequently asked questions
Your question isn't listed? Tell us briefly what it's about.
Running it
On your infrastructure. It ships as a single-server compose bundle: the API, the gateway, the job executor, the dashboard and a TLS proxy. It runs comfortably on a 4 GB server. There is no managed hosting option today, and that is deliberate: your data stays on your servers, which is what UniCore is built for.
PostgreSQL or Microsoft SQL Server. The bundle includes a preconfigured PostgreSQL container, or you can point it at a database you already run.
Copy the example environment file, set a database password, a data encryption key and an API key pepper, place your license file next to the compose file, and start it. A one-shot updater applies migrations and seed data before the hosts come up.
Yes. Images can be built and exported as archives and installed on an air-gapped host with the offline deployment script.
Releases are tagged and published as container images, so an update is a pull and a restart, with the schema updater running first. Plugin updates are separate and deliberate: a newer plugin binary only marks an update as pending until you run the upgrade.
Licensing
Per module. There are independently licensable modules, grouped into packages so you only pay for the scope you use. Your license file states the tier, the licensed modules, quota ceilings, a validity window and a grace period.
There is a grace window rather than a cliff. After it, the modules that are no longer licensed stop serving requests. The platform keeps running, and your data stays where it is.
Yes. Licenses can be issued time-limited with a grace window, which is how evaluation and pilot deployments are handled. Talk to us about the scope you want to try.
Licenses are signed with ML-DSA-87, the post-quantum signature scheme standardized as FIPS 204. There is no classical co-signature to fall back on, and the signing context is domain-separated so a license signature cannot be valid for anything else.
Data and compliance
You do. UniCore runs on your infrastructure and does not send customer data back to us. That is the whole premise of the product.
Resource payloads are encrypted at rest with a key you supply at deployment time and that never leaves your environment.
Account erasure is a core platform operation: it anonymizes what must be retained, hard-deletes what must not, and publishes a record that installed plugins react to so their own data is cleaned up too. Data export is available alongside it.
Yes. Auditing covers changes and reads, and is configurable per entity rather than all-or-nothing.
Building on it
Only if you write plugins, which are .NET assemblies. The API relay path has no such requirement: your API can be written in any language, because UniCore never runs your code. It sits in front of it.
Yes. The SDK is a package and a build-time analyzer enforces the boundary between a plugin and the platform, so a third party can build and ship one without ever seeing the platform source.
Current state: user-defined endpoints only execute data queries, not arbitrary scripts or stored procedures. Resource storage is database-backed, so there are no cloud storage adapters yet. Card payments run through Stripe; PayPal and generated PDF invoices are not implemented. And the plugin SDK has no file-storage or document-rendering facade yet.
Onboarding, plugin bootstrapping, operator training and a go-live review are available as fixed-scope services. They are optional: the platform is documented. The services are most useful for your first production deployment.