Kosmera Runtime: one application foundation, built once
The Runtime provides the services business applications need before they can do useful work. Teams spend less time building and reviewing the same infrastructure code in each new application.
Every business application needs the same groundwork: a signed-in user, a session, the right tenant and organization, access to data, and a way to serve its UI. When each application builds this independently, whether by hand or with AI, the organization pays for the same implementation and the same review again and again.
Kosmera Runtime runs inside each Kosmera application's container and provides this groundwork in the same way for all Kosmera applications.
What this means for your organization
Less repeated implementation
Sign-in, sessions, tenant resolution, and data access are not rebuilt for each new application.
Less infrastructure code to review
Shared services are part of the platform, so application reviews can concentrate on what the application itself adds.
Consistent behavior
Kosmera applications sign users in, resolve their organization, and access data in the same way.
Documents without a separate integration per app
Document storage and PDF OCR are available to Kosmera applications through the platform.
What the Runtime provides
All of these are available to Kosmera applications today.
Identity handoff with Space
IdentityUsers sign in through Kosmera Space. The application receives their identity through a secure login redirect and an authorization-code token exchange.
Applications don't need their own login, and they never see user passwords.
Sessions
IdentitySession handling is provided by the Runtime.
Kosmera applications share the same session behavior instead of each implementing its own.
Tenant and organization resolution
ContextThe Runtime resolves the current tenant and organization for each request and provides that context to the application.
Application code starts with the right tenant and organization already known.
Data access
DataApplications read and write data through the Runtime, on the server side.
One data access path, instead of a different one in each application.
UI asset serving
DeliveryThe Runtime serves each application's UI. Shell applications and standalone applications are published and served the same way.
Teams choose their frontend approach without changing how applications are delivered. About standalone apps
Document handling
Many business processes depend on documents such as contracts, invoices, and scanned forms. The Runtime provides document capabilities so applications do not each integrate their own storage and OCR.
Document storage
Available todayDocuments are stored and archived by the platform, so applications do not run their own file storage.
PDF text extraction and OCR
Available todayText is extracted from PDF documents, including scanned PDFs, using OCR. PDF is the supported format.
External service dependency
OCR is performed by Google Document AI, a Google Cloud service. Documents processed for OCR are sent to that service. Processing location and data-handling requirements are reviewed with you during evaluation.
Where your teams focus their review
With the foundation shared, your review effort goes where it matters most: what each application adds.
- Application-specific business logic
- Access configuration: who can use the application and its data
- Integrations with other systems
- Your organization's own security and release review for each application
The result
With Kosmera, the groundwork business applications need is provided by the Runtime instead of rebuilt in each project. Application teams, and the AI tools they use, concentrate on the business process.
Less infrastructure to build, and reviews focused on what each application adds.