Tenant separation, roles, and traceability — the foundation of every module.
All modules share a secure platform: separated customer data, fine-grained permissions, traceable changes, and operation in Germany.
What the module means in practice — beyond the feature list, with concrete day-to-day value in the panel.
Tenant separation is built into the core: each customer account has its own data scope. Other tenants are neither visible in the UI nor reachable via interfaces — essential for SaaS operation and compliance.
Roles and fine-grained permissions control who sees and edits accounting, service, or export. Invite users by email; relevant changes are traceable in the log.
Hosting in Germany, GDPR-oriented processes, and configurable print, email, and text templates per tenant — without deployment for layout changes.
Global search, background jobs for exports and email, plus webhooks and the Account API complement daily work: one search box instead of module switching, reliable processing of large packages, connection of your own systems.
What you can do in this module — no fluff. Details for individual panel features are under Features.
Each customer account has its own data space. Other tenants are not reachable in the UI or via APIs.
Rights per module and action — accounting, service, or admin only see what their role allows.
Relevant events are traceable — a basis for internal audit and compliance questions.
Invite team members, assign roles, and manage access centrally — scalable as you grow.
Letterhead, layouts, SMTP, and text templates per tenant — without code deployment.
One account-wide full-text search across documents, contacts, service orders, reports, bank transactions, and more — a single search box instead of switching modules, strictly scoped to your own tenant.
Large exports and email sending run in the background — the UI stays usable meanwhile.
Notify external systems of Jupiter events and connect standard integrations — alongside the Account API.
Trust
Clear answers to common questions about location, GDPR, and operations — without marketing fluff. The short overview is also on the homepage and in the footer.
Cloud operation with data centers in Germany — your tenant data stays under German jurisdiction.
Jupiter ERP runs in German data centers. Processing and storage align with German law — relevant for SMBs that do not want a US-only cloud for business data.
Infrastructure is designed for availability and tenant separation: isolated accounts, controlled access, operation by a German provider.
For enterprise customers, dedicated environments, private networking, or extended residency requirements are available on request.
Product and operations by Oleart IT Solutions GmbH in Hamburg — built for the German mid-market.
Jupiter ERP is developed and operated by Oleart IT Solutions GmbH in Hamburg. Requirements from trades, services, and retail feed directly into the roadmap and support.
Support, contracts, and contacts are in Germany — no anonymous US helpdesk for your core business.
The panel’s primary language is German and the product addresses German documents, taxes, and interfaces such as DATEV export and ZUGFeRD.
Related: About Jupiter
Privacy to EU standards: processing under GDPR, a transparent privacy policy, and a DPA for data processing.
Personal data is processed under GDPR and the German BDSG. The privacy policy describes purpose, legal bases, retention, and your rights as a data subject.
When you use Jupiter for customer data, you are usually the controller — we support you as processor with technical and organizational measures.
A data processing agreement (DPA) under Art. 28 GDPR is provided for business customers — details and process are in the privacy policy.
Related: Privacy policy
Each account is isolated at data level — other customers’ data is not accessible.
Tenant separation is core to the design: every customer (account) has its own data space. All access runs in that tenant’s context.
Documents, contacts, or files from other tenants cannot be viewed — a central protection goal for SaaS operation.
Roles and permissions further limit what users may see and change within their tenant.
Panel and API access over TLS — data protected in transit.
Access to the Jupiter panel and APIs uses HTTPS/TLS. Credentials, document content, and API payloads are protected during transfer.
The same applies to integrations and custom apps: sign-in and data transfer only over encrypted connections.
Complement TLS with strong passwords, limited user accounts, and IP restrictions on your side where needed.
Audit-ready document storage, logging, and period logic — a basis for proper processes.
Jupiter supports GoBD-oriented workflows: PDF archiving of documents, traceable document chains, and — in the accounting module — period logic with locking.
Change logs document relevant events for internal audit and questions from your tax advisor.
GoBD compliance also depends on your internal processes and organization — software provides the technical foundation, not a compliance guarantee on its own.
Related: GoBD overview
Data processing agreement (Art. 28 GDPR) for business customers — on request or as part of the contract.
If you process personal data of your customers or employees in Jupiter, you often need a DPA with us as processor.
The agreement covers instructions, sub-processors, measures, breach notification, and deletion — aligned with the Jupiter platform.
Contact us via sales or support channels when needed; the privacy policy lists the responsible party.
Related: Privacy policy
Your business data is not sold to third parties for advertising or profiling.
Business data in Jupiter serves contract fulfillment — invoices, contacts, service, exports. We do not sell tenant data to brokers or ad networks.
External providers (e.g. hosting, email) are used only for operations and bound as processors where personal data is processed.
You retain control of your content; export and termination are defined in the contract documents.
Related: Privacy policy
Contract and use under German law — provider based in the Federal Republic of Germany.
Terms and conditions are governed by German law. Jurisdiction and contracting party are in Germany.
That simplifies matters for German SMBs compared to US terms of service with foreign jurisdictions.
Clarify specific contract questions with sales or support; legal documents are available on the website.
Related: Terms & conditions · Terms of use
Target market and compliance: German documents, DATEV export, and e-invoicing (ZUGFeRD) in the product focus.
Jupiter primarily serves companies in Germany and the EU: currencies, tax codes, document types, and number ranges follow German practice.
Modules such as accounting export (DATEV-compatible) and e-invoicing (ZUGFeRD 2.2 / EN 16931) reflect local requirements.
APIs still enable international integrations — tenant separation and access control remain central.
Related: E-invoicing (ZUGFeRD)
Questions? Contact us
How teams use Platform day to day.
These modules complement Platform in typical workflows.
Start for free — choose plan, term, and add-ons in the app afterwards. Custom adaptations or API integration? Get in touch.
