AIN Research Enterprise
The AIN Research Enterprise library is the commercial, multi-tenant collaboration layer for the Autonomous Intelligence Network (AIN). It extends the open-source ain-research daemon to securely proxy data into an isolated Cloud SQL database environment.
Features
- Cloud SQL Sync: Transparently intercepts local SQLite writes and routes downloaded research papers to a hosted PostgreSQL instance.
- Multi-Tenant Isolation: Uses Master-Tenant schema separation. Organizations get their own securely provisioned database instances on-the-fly.
- Firebase Auth: Secures the CLI access. Researchers must authenticate to push articles into their organization's tenant DB.
- Enterprise Runner Monkey-Patching: Effortlessly integrates with the open-source library without requiring codebase forks.
Quickstart
# 1. Install the CLI
pip install ain-research-enterprise
# 2. Authenticate with your enterprise credentials
ain-enterprise setup --email team@myorg.com --password mysecurepass
# 3. Verify your configuration status
ain-enterprise status
# 4. Launch the Enterprise Daemon
ain-enterprise run
Architecture
This package injects an interceptor script (runner.py) into the ain-research core. It modifies db_manager.enqueue_item at runtime to prevent local markdown/file creation and instead pushes the payload directly over SQLAlchemy into your Cloud SQL database.
Support
Built by the AIN Research Team.
Metadata
Release files for ain-research-enterprise 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ain_research_enterprise-0.1.0.tar.gz | 180.5 kB | Without provenance | Details for ain_research_enterprise-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ain_research_enterprise-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ain_research_enterprise-0.1.0-py3-none-any.whl |
Total release size: 187.3 kB
Release files / ain_research_enterprise-0.1.0.tar.gz
| Download URL | ain_research_enterprise-0.1.0.tar.gz |
|---|---|
| Size | 180.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bdd1173a993690c3ddc05da742337a29248837e0f6a4519f1485fe9983d51f14
|
|
BLAKE2b-256 checksum How to use checksums |
6bb973e7ad1f6b5f3199f218adda85de3c7e5be03afedfe42394ff31b6e6310f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ain_research_enterprise-0.1.0-py3-none-any.whl
| Download URL | ain_research_enterprise-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
245dfc1439143689b2419b11b5b752239aa2a902b99beb2fe47be2c275a9adbf
|
|
BLAKE2b-256 checksum How to use checksums |
382fd1a02b8809deb5346e38e5753e8123796f3ca2c187b5ef8caa7ec5b33c17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ain-research-enterprise 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.