Frequently asked questions
Your question isn't listed? Tell us briefly what it's about.
Selling and billing
Your API stays as it is. A relay publishes it through UniCore's gateway and puts sign-in, permissions and limits in front of it. Routes come from your OpenAPI document or are entered by hand. UniCore adds your upstream credentials itself, so they stay hidden from callers. Streaming and WebSockets are forwarded. Plans, usage metering and billing then apply to the calls through the relay.
By card through Stripe or by bank transfer. You connect your own Stripe account, so customers pay you directly and UniCore takes no share of your sales. The first checkout saves the card, and later invoices are charged automatically. You record bank transfers yourself. Further payment providers can be added on request.
VAT is decided per sale. UniCore supports rates per country, the small-business rule of § 19 UStG and EU reverse charge with a VIES check of the customer's VAT ID. Sales go only to countries you have set a rate for, so a sale is never taxed at zero by accident. Every invoice and credit note is a PDF/A-3 file with the e-invoice data of EN 16931 attached (ZUGFeRD, Factur-X), and an XRechnung when the buyer gives a Leitweg-ID. Invoices are issued as soon as seller and buyer data are complete. You enter tax rates and seller details yourself, ideally together with your tax adviser.
You choose per limit. A hard stop answers HTTP 429 with the reset time and a Retry-After header. An empty credit balance answers HTTP 402. With overage, usage beyond the included allowance is billed when the period ends, per unit, tiered or by volume. This applies once the customer has switched pay-as-you-go on and accepted the prices. A spend cap lets you limit overage. Once it is reached, the API answers 429 as well, just as it does for rate limits.
Yes. The storefront package gives your web team React components for pricing, basket, checkout, usage, invoices and the 14-day withdrawal, plus a generated TypeScript client for the rest. You embed them in your own site, and a finished reference portal shows how. A plan change takes effect at the end of the current billing period.
A card charge is attempted up to four times, with one, three and five days between attempts. Three days after the first failed charge the subscription is suspended and access is paused while the remaining attempts continue. As soon as the customer pays, the subscription is reactivated. If no payment arrives, it ends 30 days after suspension. All of these periods are defaults you can adjust. Your customers get billing notices by email and in the app.
Currently, users sign in with a password or through Google, Microsoft or any OIDC provider your tenant connects, such as Keycloak. Apple sign-in is available in mobile apps. Password sign-in stays available next to an external provider. You can limit access by IP address, and API callers use API keys instead of passwords. SAML and two-factor sign-in are planned as an extension.
Plan changes currently take effect at the end of the billing period, without proration. One-time plugin charges are not invoiced. Payments run through the payment provider Stripe. Further providers and billing options can be added on request, so feel free to get in touch.
Running it
On your own server, as the single-server compose bundle or as four separate services plus the dashboard. The bundle runs PostgreSQL, a one-shot schema updater, the API, the gateway, the job executor, the dashboard and an optional nginx TLS proxy. Its memory limits add up to about 2.7 GB, tuned for a 4 GB host. UniCore is built to run on your own infrastructure, so your data stays on your servers. If you would like a managed setup, feel free to get in touch.
PostgreSQL or Microsoft SQL Server, each with its own migrations. The bundle ships a preconfigured PostgreSQL container. For SQL Server or a PostgreSQL you already run, you set the database type and connection string and leave the container out.
You run deploy.sh. The script generates the database password, the data encryption key and the API key pepper, asks for the first administrator's password, writes the host configuration and starts the stack. You supply the license file, a read token for our container registry and, with the proxy, a domain and a TLS certificate. A one-shot updater migrates the database and seeds it before the hosts start.
Yes. On a workstation with internet access you pull the images, save them as archives, copy them to the server and run the offline deployment script. The install and the license check run fully offline on the server. Only card payments through Stripe, the VIES check of VAT IDs and sign-in through Google or Microsoft need an internet connection, once you use them.
Pull the new images and restart. Pin a version tag instead of latest. The one-shot updater migrates the database before the hosts start, so back up the database first. You control plugin updates separately. A newer plugin binary is marked as a pending update, and you run the upgrade when it suits you.
Back up the database. Also keep copies of the license file and the .env file. The .env file holds the data encryption key and the API key pepper. Both values have to stay unchanged. Encrypted values stay readable only with the same key, and issued API keys stay valid only with the same pepper.
Licensing
Per module. Modules are licensed individually and grouped into packages, so you pay only for the scope you use. Your license file names the licensed modules, a start and end date and an optional grace period, and every host checks them.
A license is checked when a host starts. During the grace period after the end date, hosts still start. After that, a host that is started or restarted needs a new license file and tells you the reason at startup. Running hosts keep working without a further check. Note the end date so the new license file is ready in time. Your data stays where it is in any case.
Yes. We issue a time-limited license for the modules you want to try, with an optional grace period. It differs from a production license only in its modules and end date. Tell us the scope you want to test.
Licenses are signed with ML-DSA-87, the post-quantum signature scheme standardized as FIPS 204. Verification relies on this scheme alone, with no classical co-signature to fall back on. The signing context is specific to licenses, so a license signature is valid as a license only.
The check runs fully offline. A host checks its license file against a public key built into the software, with no connection to us. An issued license therefore stays valid until its end date and cannot be revoked remotely.
Data and compliance
You do. UniCore runs on your infrastructure, so customer records, invoices and usage data stay in your database. As a vendor you are the seller, with your own Stripe account and your own invoices.
Selected columns are encrypted with AES-GCM under a key you set at deployment. These are stored files (resource payloads) and secrets such as upstream API credentials, Stripe keys, sign-in client secrets, webhook secrets and messenger tokens. Other data, such as users and invoices, is protected by the database or disk encryption of your infrastructure. Keep the key safe and unchanged, because encrypted values stay readable only with it.
A user can export their data as JSON and ask for deletion. The account is locked at once and anonymized after a grace period. Until then the deletion can be canceled. Open usage is billed on a final invoice first, and issued invoices stay whole as accounting records. Plugins read a list of erased users that is free of personal data, and delete their own data.
Yes, with the Auditing module of the Platform package. It records changes and reads, and you configure it per entity rather than all-or-nothing.
Building on it
Only if you write plugins, which are .NET assemblies. On the API relay path the choice is yours. Your API can be written in any language, because UniCore sits in front of it and leaves its code untouched.
Yes, they can build one. The SDK is a package and an analyzer keeps a plugin apart from the platform source, so a third party can write one with the SDK alone. A plugin runs as fully trusted code inside the host, with the host's rights. That is why you decide whom to trust. Production hosts load only plugins signed with a key you chose to trust, and uploading is reserved for administrators of your main tenant.
SAML and two-factor sign-in are planned as an extension. We build further features as needed or on request. These include a sandbox or marketplace for third-party plugins, custom endpoints beyond data queries and forms, cloud storage adapters alongside file storage in the database, SMS as a further channel next to email, Telegram, Discord and WhatsApp, additional pipeline blocks such as loops, waits, multi-way switches and code blocks, and a managed setup. What applies to selling and billing is answered above, under "Selling and billing". Feel free to get in touch.
Five fixed-scope services: onboarding and go-live, an API monetization sprint (relay, plans, quotas), a plugin bootstrap sprint, operator training and a go-live readiness review. They are optional, because the platform is documented, and help most with your first production deployment. The pricing page lists each with its scope.