TITAN PROVIDERS

Shared capabilities.
No need to build them
from scratch.

From data and files to cryptography and email.
Essential capabilities are ready.
You and AI can focus on your service.

Explore capabilities
01 / SAME FOUNDATION

Different languages.
The same implementation.

Language SDKs invoke common Providers. Use the same feature contracts instead of implementing separate capabilities in JavaScript and Java.

02 / REUSE THE IMPLEMENTATION

Beyond code snippets.
Reuse the capability itself.

The platform manages common capabilities and processing rules. Add business code on the same foundation in new modules and applications.

03 / BUILD WITH AI

Different AI tools.
Consistent code conventions.

AI follows platform guides and SDKs. Fewer ad hoc choices for storage, cryptography and transport help keep code consistent.

READY FOR YOUR APPLICATION

Capabilities to add to your application.

Choose what you need.
Connect it to your business.

@titan/kv

KV

01

Store small data properly.

Store and retrieve settings and small JSON values by key. Modules in the same application share the same storage.

  • Store, read and delete JSON
  • Set expiration times
  • Detect conflicts with version conditions
Business codeKV ProviderApplication JSON data

Use casesRecent task state, user settings and temporary application data

JavaScriptJavaGo
Before you start

Define keys and data structures for your application.

Your application checks per-user access and business rules.

@titan/db

Database

02

Write SQL. Leave connections to the platform.

Use SQL files and named parameters with connected databases. The same SQL conventions apply across languages.

  • Execute SQL by name
  • Query, insert, update and delete
  • Explicit transactions
SQL name + parametersDB ProviderConnected database

Use casesMembers, orders, assignees and business tables

JavaScriptJava
Before you start

Connect a database to the application and assign it to modules.

Developers decide table design and business meaning.

@titan/file

File

03

A shared approach to attachments.

Get temporary upload and download URLs and file metadata. Connect file transfers to your business data using a consistent approach.

  • Issue upload and download URLs
  • Read file names, sizes and metadata
  • Delete files
App server authorizationFile ProviderFile transfer

Use casesTask photos, form attachments and result downloads

JavaScriptJava
Before you start

Implement file access APIs and user authorization in the app server.

Associate the uploaded file ID with business data.

@titan/http

HTTP

04

One convention for external services.

Call public HTTPS APIs from the server. Shared request and response formats keep integration code consistent.

  • HTTP requests including GET and POST
  • Common response format
  • Configurable request timeout
App serverHTTP ProviderExternal HTTPS API

Use casesWeather, public data and external business services

JavaScriptJava
Before you start

Prepare the external service's terms and required API credentials.

Does not replace the external service's authentication or fees.

@titan/crypto

Crypto

05

Protect values with shared, tested capabilities.

Password hashing, token and session operations, encryption and signing. Avoid rebuilding algorithms and key handling for every feature.

  • Hash and verify passwords
  • Token and session operations
  • Encrypt, decrypt and sign
Value to protectCrypto ProviderProtection / verification result

Use casesPassword verification and protected application data

JavaScriptJava
Before you start

Design the application's login flow and session retention and revocation rules.

Does not automatically implement your entire membership or login system.

@titan/email

Email

06

Business email, from sending to status.

Send text and HTML email through the application's SMTP settings. Check each request's sending status and distinguish duplicate submissions.

  • Text and HTML email
  • Request-ID deduplication
  • Check sending acceptance
Recipient + messageEmail ProviderApplication SMTP server

Use casesWelcome messages, notifications and processing results

JavaScriptJava
Before you start

The owner registers SMTP settings, checks the connection and enables sending.

Accepted for sending does not mean delivered to the inbox. Sending limits apply.

@titan/messaging

Messaging

Development environment

Connect modules through events.

Publish application events and process follow-up tasks in subscribing modules. The platform handles delivery and validation; your application handles business logic.

  • Publish application events
  • Configure module subscriptions
  • Shared receive and validation path
Publish eventMessagingSubscriber business logic

Use casesPost-order processing and change notifications between modules

JavaScriptJava
Before you start

Define events and subscribers, then implement and deploy business handlers.

Available in the currently supported development environments and templates.

@titan/batch

Batch

Preview

Move long-running work into batches.

Execute batch modules separately from online requests and check their results. Manage scheduled and manual tasks through one workflow.

  • Request batch execution
  • Check execution status and results
  • Integrated batch management
Execution requestBatch ProviderBatch action + result

Use casesScheduled aggregation, data processing and follow-up tasks

JavaScriptJava
Before you start

Implement and deploy actions and business logic in a separate batch module.

The caller SDK supports JavaScript and Java. This is separate from the languages supported by batch modules themselves.

@titan/* names are JavaScript packages. Java and Go use their respective libraries. They share feature contracts, but not every capability has an SDK for every language.

SAME BEHAVIOR. YOUR LANGUAGE.

Different syntax. The same work.

For example, saving application settings.
KV's core implementation stays the same across languages.

MY APPLICATIONJavaScript Business code

“Save and read a welcome message.”

TITAN SDK → PROVIDERThe same KV implementation

Store · Read · Expire · Conditional updates

APPLICATION DATAShared application storage

No need to rebuild storage for each language.

This example illustrates the architecture. It does not save data or install an SDK.

YOUR LOGIC, ON OUR FOUNDATION

Even for sign-up,
start with shared foundations.

Developers implement business rules such as sign-up conditions, validation and user authorization. Connect ready-made capabilities for password protection, data access and email.

01Protect passwordsCrypto →
02Store member detailsDatabase →
03Request welcome emailEmail →

An example design. The application implements membership and authentication flows; Providers do not replace a complete sign-up service.

A SHARED GUIDE FOR YOU AND AI

Give AI the same foundation.

See an AI development scenario →
“Store member details in the connected database.
Protect passwords with Titan Crypto.
Send a welcome email after sign-up.”
1Identify the capabilities

AI checks the platform guide for available capabilities and required settings.

2Connect through common SDKs

Choose an SDK in a supported language and follow its invocation contract.

3Focus on business code

Focus on business rules, error handling and tests, then verify the results.

LESS REINVENTING. MORE BUILDING.

What you need to build:
your own service.

Shared capabilities on projectroom. Business code by you and AI.

See how to get started →My applications ↗